We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
None
The text was updated successfully, but these errors were encountered:
If nobody is working on it, I'll take it.
Sorry, something went wrong.
We have now receive_timeot and heartbeat, should be enough
receive_timeot
heartbeat
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.
No branches or pull requests
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.The text was updated successfully, but these errors were encountered: