Andres G. Aragoneses db362a0ea3 Core: avoid possible infinite loop if switching to same DC ... People are reporting that under some circumstances, an infinite loop could happen when TLSharp tries to handle a reconnection to a different DC, if the DC instructed to be used is the same as the one that was used in the last connection. Not sure how could this happen (although the analysis present in this github issue [1] might help understand it), but this commit helps to make TLSharp fail fast (with an exception) instead of an infinite loop from now on, which will help avoiding people file issues such as [2] and [3] and instead maybe file a proper bug report easier to understand, to try to fix the underlying root cause. [1] https://github.com/sochix/TLSharp/issues/719 [2] https://github.com/sochix/TLSharp/issues/803 [3] https://github.com/sochix/TLSharp/issues/839		2020-04-01 14:59:56 +04:30
..
Auth	Fix spelling of Receive	2016-07-20 08:15:28 +01:00
MTProto	Update Everything	2016-09-22 17:01:59 +03:30
Network	Core: fix 2 warnings	2020-04-01 14:59:56 +04:30
Properties	TLSharp and Tests	2015-09-28 10:01:17 +08:00
Requests	Generator Must Respect MS .NET API guidelines	2017-11-09 19:37:09 +08:00
Utils	Generator Must Respect MS .NET API guidelines	2017-11-09 19:37:09 +08:00
DataCenter.cs	Core: avoid possible infinite loop if switching to same DC	2020-04-01 14:59:56 +04:30
packages.config	Redesign Everything	2016-09-24 17:08:26 +03:30
Session.cs	Core: avoid possible infinite loop if switching to same DC	2020-04-01 14:59:56 +04:30
TelegramClient.cs	Core: avoid possible infinite loop if switching to same DC	2020-04-01 14:59:56 +04:30
TLSharp.Core.csproj	Core: avoid possible infinite loop if switching to same DC	2020-04-01 14:59:56 +04:30
TLSharp.Core.nuspec	another fix	2016-10-29 17:13:28 +03:00