Perhaps as a result of ping failures (Issue #43) and subsequent socket close/disconnect, my client application using EngineIoClientDotNet v1.0.3 will see a System.Net.WebException ('The remote server returned an error: (400) Bad Request').
I don't know code well enough but thought a try-catch for AggregateExceptions might mitigate some of these unexpected exceptions.
Perhaps as a result of ping failures (Issue #43) and subsequent socket close/disconnect, my client application using EngineIoClientDotNet v1.0.3 will see a System.Net.WebException ('The remote server returned an error: (400) Bad Request').
I don't know code well enough but thought a try-catch for AggregateExceptions might mitigate some of these unexpected exceptions.