We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
1 parent 56f0911 commit 0acea45Copy full SHA for 0acea45
README.md
@@ -129,8 +129,8 @@ gorilla/websocket requires you to constantly read from the connection to respond
129
even if you don't expect the peer to send any messages.
130
131
The ping API is also much nicer. Unlike gorilla/websocket, you don't need to register a
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.
+callback for pongs. There is Ping method on the Conn that sends a ping and waits for the pong.
+Callbacks tend to encourage awkward control flow.
134
135
In terms of performance, the differences depend on your application code. nhooyr/websocket
136
reuses buffers efficiently out of the box if you use the wsjson and wspb subpackages whereas
0 commit comments