proxy -> telegram connection multiplexing

It looks like it’s possible to multiplex many client -> proxy connections into single proxy -> telegram server connection based on RPC connection ID

https://github.com/alexbers/mtprotoproxy/blob/ed227da7c3afe67c876cd922661eedd0ec87da78/mtprotoproxy.py#L330 https://github.com/alexbers/mtprotoproxy/blob/ed227da7c3afe67c876cd922661eedd0ec87da78/mtprotoproxy.py#L358

You just have to maintain mapping between client -> proxy and proxy -> telegram sockets and send packets as a whole. And, probably, you will need to have some kind of proxy -> telegram connection pool (separate pool for each dc_id)

[alexbers]

Nice graphs! I think I will forward small messages (<4096 bytes) directly and big messages by parts. Also, for big messages it is possible to implement speed throttling on tcp level.

I tested the official proxy and I managed it to occupy a 1MB per client. The interesting thing, when I tried to test with about 300 clients, the official client always crashes:

I sent the program which predictably crashes a proxy by its address to the official proxy authors, hope they will fix soon.

[seriyps]

The messages can have up to 1MByte size.

Isn’t it 64Mb? https://github.com/alexbers/mtprotoproxy/blob/master/mtprotoproxy.py#L304

3 bytes = 24bits and you multiply it by 4, so: 2**24 * 4 / 1024 / 1024 = 64