TLSharp/TLSharp.Core
Andres G. Aragoneses 881bdd27a5 Core: make MtProtoSender.GenerateSequence() thread-safe
Even if you're not supposed to use multiple threads with TLSharp,
it might be worth it to try to make this sequence increment in
a thread-safe way. Race conditions are always bad even if you know
you are not supposed to use something in a certain way...

@Laituex was having a ErrCode=32 'msg_seqno too low' problem and this
is the first thing we looked at (even if he swore that he was not
using different threads to access the telegram network)
2020-09-21 14:52:07 +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: make MtProtoSender.GenerateSequence() thread-safe 2020-09-21 14:52:07 +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