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

Close server-side websocket connection after certain period of inactivity. #1081

Closed
asvetlov opened this issue Aug 15, 2016 · 3 comments
Closed
Labels

Comments

@asvetlov
Copy link
Member

The only reliable way to make sure that socket is still alive is listening for ping message.

Server should terminate web socket if no incoming event was for timeout period.

By default the period should be None for keeping backward compatibility.

@jincreator
Copy link
Contributor

If nobody is working on it, I'll take it.

@fafhrd91
Copy link
Member

fafhrd91 commented Feb 1, 2017

We have now receive_timeot and heartbeat, should be enough

@lock
Copy link

lock bot commented Oct 29, 2019

This thread has been automatically locked since there has not been
any recent activity after it was closed. Please open a new issue for
related bugs.

If you feel like there's important points made in this discussion,
please include those exceprts into that new issue.

@lock lock bot added the outdated label Oct 29, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants