Skip to content

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

Closed
majek opened this issue May 14, 2012 · 3 comments
Closed

Optionally expect heartbeats from the client #68

majek opened this issue May 14, 2012 · 3 comments
Labels

Comments

@majek
Copy link
Member

majek commented May 14, 2012

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.

@glasser
Copy link
Contributor

glasser commented Sep 26, 2012

There was a lot of activity on this issue but it's still open. Does the feature work (and it should be closed)?

@brycekahle
Copy link
Contributor

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.

@brycekahle
Copy link
Contributor

I just added support for this in websockets (see #169). Other protocols need to follow.

@sockjs sockjs locked and limited conversation to collaborators Oct 7, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
Projects
None yet
Development

No branches or pull requests

3 participants