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 can see the router has AddSessionOpenCallback and AddSessionCloseCallback, but I have not found anything similar for the client. Is there a way for a client to know if the underlying websocket has disconnected for whatever reason?
The text was updated successfully, but these errors were encountered:
If it closes normally, you'll get a message saying as much, but if it closes abnormally (socket died), I don't think there's anything currently in the source to hook into that.
I can see the router has AddSessionOpenCallback and AddSessionCloseCallback, but I have not found anything similar for the client. Is there a way for a client to know if the underlying websocket has disconnected for whatever reason?
The text was updated successfully, but these errors were encountered: