Socket still live after client disconnect about websocket-manager HOT 6 CLOSED

I have fixed the OnDisconnected event. It will always fire now, immediately.

from websocket-manager.

Thanks @Henry00IS . Its working!

from websocket-manager.

I have the same question. how to do heartbeat?

from websocket-manager.

problem seems solved:
create your own Hub:
class myhub : WebSocketHandler { private List<User> _users {get;set;} }
then User class:
class User { timer.Elapsed += e => { if(elapsed > timeout) onTimeout.emit(); else if(elapsed % interval == 0) onHeartBeat.emit(); } }
and in myhub class override onConnected method, you have to create an User and listen to both timeout/heartbeat events once new connection arrives.
and once you got timeout event emitted from User class, close the connection and do clear.
and do InvokeClientMethodAsync to send heartbeat event for once you got heartbeat event from the user class.

the client should listen to "heartbeat" event and inovke back (send { methodName: "ReceiveHeartBeat" }) to server again, and in myhub class write "ReceiveHeartBeat" method, the WebSocketHnadler (the base class) will find the corresponding method and invoke it for you, in that method, reset user.elapsed = 0.

from websocket-manager.

from websocket-manager.

@awosztyl thank you, I have just read it.
but I wonder why only catch the exception for "All" method eg. sendmessagetoALLasync
this error will only occur when the server wants to deal with the client. so what if the server does not send any thing to the client for a long time?

by the way I have a question, what is the correct way to pass the current logged-in user to the WebSocketHandler?

from websocket-manager.