From 8f6784adf5bca1dbab98ba1ec69ab52050633ca1 Mon Sep 17 00:00:00 2001 From: Daniil Gentili Date: Wed, 17 Jul 2019 20:34:03 +0200 Subject: [PATCH] Update UPDATES_INTERNAL.md --- docs/docs/UPDATES_INTERNAL.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docs/UPDATES_INTERNAL.md b/docs/docs/UPDATES_INTERNAL.md index d6349ad9..24d349ae 100644 --- a/docs/docs/UPDATES_INTERNAL.md +++ b/docs/docs/UPDATES_INTERNAL.md @@ -1,12 +1,12 @@ --- title: Working with updates in MTProto -description: To store information about an account session and avoid re-logging in, serialization must be done. +description: Apart from the basic operations required to work with MTProto update sequences, implementations also have to take care to postpone updates received via the socket while filling gaps in the event and Update sequences, as well as avoid filling gaps in the same sequence. image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png --- # Working with updates in MTProto -Apart from the baisc operations [required to work with MTProto update sequences](https://core.telegram.org/api/updates), Implementations also have to take care to postpone updates received via the socket while filling gaps in the event and Update sequences, as well as avoid filling gaps in the same sequence. +Apart from the basic operations [required to work with MTProto update sequences](https://core.telegram.org/api/updates), implementations also have to take care to postpone updates received via the socket while filling gaps in the event and Update sequences, as well as avoid filling gaps in the same sequence. An interesting and easy way this can be implemented, instead of using various locks, is by running background loops, like in [MadelineProto](https://github.com/danog/MadelineProto/tree/master/src/danog/MadelineProto/Loop/Update).