Connection Status while connecting
See original GitHub issueHi, so I’m using the latest version of your library and noticed that the event handling of connect/disconnect is not working properly.
If I connect using “Client.StartWithTimeoutAsync()” and have setup event handlers like
client.ServerConnected += OnConnected;
client.ServerDisconnected += OnDisconnected;
I will get multiple events, like hundreds, like this
Connected
Disconnected
Connected
Disconnected
Connected
Disconnected
...
Which is undesirable, especially if those event handlers are used to trigger certain things or as a source of binding it to a button / status text.
In my humble opinion the events should only be invoked if the connection is truly “connected” or “disconnected”.
Issue Analytics
- State:
- Created 4 months ago
- Comments:14 (6 by maintainers)
Top Results From Across the Web
Check your network connection status
Windows 11 lets you quickly check your network connection status. Select the Start button, then type settings. Select Settings > Network & internet....
Read more >Check the Network Connection Status of Wireless Devices
Check the connection when an error message appears on the screen or to troubleshoot issues with network-connected applications that crash or ...
Read more >Check the status of your network on Mac
Check the status of your network on Mac. You can check the status of your network connection, such as Ethernet or Wi-Fi, using...
Read more >Network Connection Status - Class
You can check the connection status for everyone in the session, including yourself. There are two places you can watch the status of...
Read more >Connecting to a system from the connection status bar
The connection status icon is red, indicating that the connection was not successful. An error message is displayed providing a reason for the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
No waste of time at all! Please let me know if I can help in any way going forward. Cheers
I’m so sorry… I should have checked if something was listening on that port. And yes, there is an application listening on the port… This can be closed 😄
But still, I think the check if the task is faulted can stay. Sorry to waste your time 😃