Skip to content
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

Automatic hearbeat using WS pings/pongs #32

Closed
oberstet opened this issue Mar 23, 2013 · 5 comments
Closed

Automatic hearbeat using WS pings/pongs #32

oberstet opened this issue Mar 23, 2013 · 5 comments
Assignees

Comments

@oberstet
Copy link
Contributor

There should be an automatic heartbeat feature to quickly recognize broken connections.

@oberstet
Copy link
Contributor Author

This is an important one. Server-initiated WS ping/pong will only allow the server to detect broken connections quickly .. not the client. One needs client-initiated WS ping/pong in addition. You need both.

#92

@william-ferguson-au
Copy link
Contributor

You don't necessarily need both. You just need the client to record the last time it received a ping from the server and have a thread that uses that as a timeout to kill the connection.

@oberstet
Copy link
Contributor Author

@william-ferguson-au interesting idea. could work. I guess I'd still call it a "workaround", but still. unfort., it won't work in browsers (unrelated to AutobahnAndroid, but relevant for AutobahnJS), because the W3C WS API doesnt expose any ping/pong (not receiving, not sending). anyway: we do want to have client initiated (and timed out) WS ping/pong in AutobahnAndroid v2 ..

@om26er
Copy link
Contributor

om26er commented Sep 26, 2017

I am working on this with some ideas, should have a solution soon. This should also deal with #36 and will ultimately pave way for #280

@om26er
Copy link
Contributor

om26er commented Sep 28, 2017

fixed by #287

@om26er om26er closed this as completed Sep 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants