TLSharp/TLSharp.Core
Andres G. Aragoneses 1b06473108 Core: save session as soon as a the sequence is incremented
Just be safe, let's not wait until other part of the code saves the
session, and let's do it right here on the spot, where we know it
changes.

@Laituex was having a ErrCode=32 'msg_seqno too low' problem and this
is the second thing we suspected to be the culprit, because if there's
any issue (e.g. exception) that makes the session not be saved after
the sequence got incremented, then an old sequence would be used the
next time upon loading an old session file.
2020-09-21 14:56:11 +08:00
..
Auth Improvements for async methods 2020-01-28 10:10:49 +03:00
Exceptions Exceptions moved to separate folders (#899) 2020-01-25 02:28:37 +08:00
MTProto Remove unnecessary dependencies 2020-04-05 19:33:18 +08:00
Network Core: save session as soon as a the sequence is incremented 2020-09-21 14:56:11 +08:00
Properties TLSharp and Tests 2015-09-28 10:01:17 +08:00
Utils style: more consistent naming removing underscores 2020-01-31 14:39:19 +08:00
DataCenter.cs DataCenter refactoring 2020-01-26 21:29:41 +03:00
DataCenterIPVersion.cs Added an IPv4/IPv6 toggle to TelegramClient constructor (#925) 2020-04-05 23:22:36 +08:00
packages.config Remove unnecessary dependencies 2020-04-05 19:33:18 +08:00
Session.cs Core: make MtProtoSender.GenerateSequence() thread-safe 2020-09-21 14:52:07 +08:00
TelegramClient.cs Core: don't consider MediaOnly DCs at reconnect 2020-04-12 01:52:25 +08:00
TLSharp.Core.csproj Added an IPv4/IPv6 toggle to TelegramClient constructor (#925) 2020-04-05 23:22:36 +08:00
TLSharp.Core.nuspec Remove unnecessary dependencies 2020-04-05 19:33:18 +08:00