We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
1 parent 308f9c2 commit bf6f475Copy full SHA for bf6f475
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. gorilla/websocket requires registering a pong handler on the Conn
132
-which results in an awkward control flow. With nhooyr/websocket you use the Ping method on
133
-the Conn that sends a ping and also waits for the pong.
+which results in awkward control flow. With nhooyr/websocket you use the Ping method on the Conn
+that sends a ping and also waits for the pong.
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