File tree Expand file tree Collapse file tree 1 file changed +2
-2
lines changed Expand file tree Collapse file tree 1 file changed +2
-2
lines changed Original file line number Diff line number Diff line change @@ -129,8 +129,8 @@ gorilla/websocket requires you to constantly read from the connection to respond
129
129
even if you don't expect the peer to send any messages.
130
130
131
131
The ping API is also much nicer. Unlike gorilla/websocket, you don't need to register a
132
- callback for pongs, there is a single exported Ping method on the Conn you use that sends
133
- a ping and waits for the pong.
132
+ callback for pongs which makes the control flow awkward. There is Ping method on the Conn
133
+ that sends a ping and waits for the pong.
134
134
135
135
In terms of performance, the differences depend on your application code. nhooyr/websocket
136
136
reuses buffers efficiently out of the box if you use the wsjson and wspb subpackages whereas
You can’t perform that action at this time.
0 commit comments