You can pass CancellationToken to IEasyClient.ConnectAsync method. But it's not respected.
EasyClient will wait a lot longer than what I specified in CancellationToken.
As far as I checked SocketConnector is not doing anything with CancellationToken.
In this PR I passed cancellation token to the Socket which is used internally.
Unfortunately, netstandard2.1 doesnt accept CancellationToken as a parameter so I added conditional compilation and implemented special code for netstandard to handle this scenario.
You can pass CancellationToken to IEasyClient.ConnectAsync method. But it's not respected. EasyClient will wait a lot longer than what I specified in CancellationToken. As far as I checked SocketConnector is not doing anything with CancellationToken.
In this PR I passed cancellation token to the Socket which is used internally. Unfortunately, netstandard2.1 doesnt accept CancellationToken as a parameter so I added conditional compilation and implemented special code for netstandard to handle this scenario.