QUARTZCODE VERTEX MODE UPDATE
QUARTZCODE VERTEX MODE CODE

Telegram owns four AS numbers to announce the IPs: AS62014, AS62041, AS59930, and AS44907. Telegram-iOS includes several seed addresses for a cold start:

It’s better for the backend to control it directly. Solutions like Geo DNS is good for very coarse-grained IP selection.

QUARTZCODE VERTEX MODE UPDATE

The app should be able to update its endpoint configuration in time. Then elastic IPs could be deployed to proxy traffic to data centers. Static IPs could be inaccessible in some regions. IP addresses and ports need to change frequently to react to network issues.The system DNS service might be unstable, or even untrustful. It’s common to NOT use domain names directly due to several reasons: It requires the client to use the correct master data center to access the user data and might use other DC ids to download images, files, etc. Telegram backend associates a registered account to a master DC id. Alias is useful to compose URIs for HTTP transport, which is not used in the iOS app. Telegram divides its backend servers into 5 data centers. Basic Concepts of Connections ) 数据中心 (Data Center ) The common best practice should be using as few connections as possible. The result surprised me: 20 TCP connections to Telegram data centers and 8 HTTPS requests to external services. How many connections are used by MTProtoKit during the first login process? I started my reading to answer a simple question:

QUARTZCODE VERTEX MODE CODE

The major parts of network code reside in modules TelegramCore and MTProtoKit. Let’s continue with the implementation details of connection management for MTProto. TCP is the only active MTProto transport on Telegram-iOS as I explained in the previous post.

Quartzcode vertex mode