You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ go get nhooyr.io/websocket
23
23
- JSON and ProtoBuf helpers in the [wsjson](https://godoc.org/nhooyr.io/websocket/wsjson) and [wspb](https://godoc.org/nhooyr.io/websocket/wspb) subpackages
24
24
- Highly optimized by default
25
25
- Concurrent writes out of the box
26
-
-[Complete WASM](https://godoc.org/nhooyr.io/websocket#hdr-WASM) support
26
+
-[Complete Wasm](https://godoc.org/nhooyr.io/websocket#hdr-Wasm) support
27
27
28
28
## Roadmap
29
29
@@ -130,7 +130,7 @@ The ping API is also nicer. gorilla/websocket requires registering a pong handle
130
130
which results in awkward control flow. With nhooyr/websocket you use the Ping method on the Conn
131
131
that sends a ping and also waits for the pong.
132
132
133
-
Additionally, nhooyr.io/websocket can compile to [WASM](https://godoc.org/nhooyr.io/websocket#hdr-WASM) for the browser.
133
+
Additionally, nhooyr.io/websocket can compile to [Wasm](https://godoc.org/nhooyr.io/websocket#hdr-Wasm) for the browser.
134
134
135
135
In terms of performance, the differences mostly depend on your application code. nhooyr/websocket
136
136
reuses message buffers out of the box if you use the wsjson and wspb subpackages.
0 commit comments