-
Notifications
You must be signed in to change notification settings - Fork 6
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
Implementation of the Ping/Pong #30
Conversation
Ported from the k6/ws
websockets/websockets.go
Outdated
|
||
data := []byte(pingID) | ||
|
||
err := w.conn.WriteControl(websocket.PingMessage, data, deadline) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the previous( k6/ws
) implementation all the methods did what they did (send/ping ) on the event loop more or less. This is not the case here send
does not actually send the message anymore it queues it to be send. Given that ping
also writes I feel like it should be off the main loop the same way the send
is
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tried to address in e1b5a46
Co-authored-by: Mihail Stoykov <312246+mstoykov@users.noreply.github.com>
What?
Porting ping/pong from the k6
Why?
Resolves: #6