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
Hello,
this is somewhat related to #15, but not completely. I noticed that sometimes bad websocket connections aren't detected by ruby.
So, best practice would be to send a "ping" in regular intervals (ws.send(Time.now.to_i, {type: :ping })) and to do something when there is no reply.
ws.send(Time.now.to_i, {type: :ping })
I could implement all that in my code, but helper functions in the simple client would be great :)
Like a way to specify the ping interval, and after what time without reply something happens. E.g. it could emit a "ping_timeout" event.
Does this make sense, is that something that would be useful for more than me? :)
Thanks Sebastian
The text was updated successfully, but these errors were encountered:
"ping_timeout", a configuration value that does nothing if nil (or 0 ?) is specified, would help existing users avoid dealing with breaking changes.
nil
0
Anyone who waiting for this feature, please comment here.
Sorry, something went wrong.
I'd love to have it
No branches or pull requests
Hello,
this is somewhat related to #15, but not completely. I noticed that sometimes bad websocket connections aren't detected by ruby.
So, best practice would be to send a "ping" in regular intervals (
ws.send(Time.now.to_i, {type: :ping })
) and to do something when there is no reply.I could implement all that in my code, but helper functions in the simple client would be great :)
Like a way to specify the ping interval, and after what time without reply something happens. E.g. it could emit a "ping_timeout" event.
Does this make sense, is that something that would be useful for more than me? :)
Thanks
Sebastian
The text was updated successfully, but these errors were encountered: