-
-
Notifications
You must be signed in to change notification settings - Fork 309
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optionally expect heartbeats from the client #68
Comments
It is undesired to send
There was a lot of activity on this issue but it's still open. Does the feature work (and it should be closed)? |
I would prefer this be a ping-pong type mechanism instead of just a timed interval of expected data from the client. The server pings every X seconds, and expects a pong within X seconds. If not, the connection is considered disconnected. |
I just added support for this in websockets (see #169). Other protocols need to follow. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
We should have an opt-in mechanism for enabling verifying heartbeats on the server.
With this option enabled the client MUST send heartbeat frames once in a while, so this involves changes in sockjs-client.
The text was updated successfully, but these errors were encountered: