You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I decided to let clients cause exceptions in server events, otherwise it's almost impossible to cover all exception scenarios - this is all great in practice, exceptions are caught by socket.io, the code is simpler
However, when an exception occurs in the server-side event handler, the client is disconnected, yet the client-side "disconnect" event isn't triggered
I want the client side "disconnect" to trigger whenever the connection is severed
Is it possible to remedy/fix this issue, I'm guessing this is a long-standing issue with ties to #2285
The text was updated successfully, but these errors were encountered:
That issue was closed automatically. Please check if your issue is fixed with the latest release, and reopen if needed (with a fiddle reproducing the issue if possible).
I decided to let clients cause exceptions in server events, otherwise it's almost impossible to cover all exception scenarios - this is all great in practice, exceptions are caught by socket.io, the code is simpler
However, when an exception occurs in the server-side event handler, the client is disconnected, yet the client-side "disconnect" event isn't triggered
I want the client side "disconnect" to trigger whenever the connection is severed
Is it possible to remedy/fix this issue, I'm guessing this is a long-standing issue with ties to #2285
The text was updated successfully, but these errors were encountered: