Repository files navigation

websocket is a minimal and idiomatic WebSocket library for Go.

This library is not final and the API is subject to change.

go get nhooyr.io/websocket@v0.2.0

• Minimal and idiomatic API
• Tiny codebase at 1400 lines
• First class context.Context support
• Thorough tests, fully passes theautobahn-testsuite
• Zero dependencies outside of the stdlib for the core library
• JSON and ProtoBuf helpers in the wsjson and wspb subpackages
• High performance
• Concurrent writes

• WebSockets over HTTP/2#4
• Deflate extension support#5

For a production quality example that shows off the full API, see theecho example on the godoc. On github, the example is atexample_echo_test.go.

http.HandlerFunc(func (w http.ResponseWriter,r*http.Request) {c,err:=websocket.Accept(w,r, websocket.AcceptOptions{})iferr!=nil {// ...}deferc.Close(websocket.StatusInternalError,"the sky is falling")ctx,cancel:=context.WithTimeout(r.Context(),time.Second*10)defercancel()varvinterface{}err=wsjson.Read(ctx,c,&v)iferr!=nil {// ...}log.Printf("received: %v",v)c.Close(websocket.StatusNormalClosure,"")})

ctx,cancel:=context.WithTimeout(context.Background(),time.Minute)defercancel()c,_,err:=websocket.Dial(ctx,"ws://localhost:8080", websocket.DialOptions{})iferr!=nil {// ...}deferc.Close(websocket.StatusInternalError,"the sky is falling")err=wsjson.Write(ctx,c,"hi")iferr!=nil {// ...}c.Close(websocket.StatusNormalClosure,"")

• A minimal API is easier to maintain due to less docs, tests and bugs
• A minimal API is also easier to use and learn
• Context based cancellation is more ergonomic and robust than setting deadlines
• No ping support because TCP keep alives work fine for HTTP/1.1 and they do not makesense with HTTP/2 (see#1)
• net.Conn is never exposed as WebSocket over HTTP/2 will not have a net.Conn.
• Using net/http's Client for dialing means we do not have to reinvent dialing hooksand configurations like other WebSocket libraries

Before the comparison, I want to point out that both gorilla/websocket and gobwas/ws wereextremely useful in implementing the WebSocket protocol correctly sobig thanks to theauthors of both. In particular, I made sure to go through the issue tracker of gorilla/websocketto ensure I implemented details correctly and understood how people were using WebSockets inproduction.

https://github.com/gorilla/websocket

This package is the community standard but it is 6 years old and over timehas accumulated cruft. Using is not clear as there are many ways to do thingsand there are some rough edges. Just compare the godoc ofnhooyr/websocket side by side withgorilla/websocket.

The API for nhooyr/websocket has been designed such that there is only one way to do thingswhich makes it easy to use correctly. Not only is the API simpler, the implementation isonly 1400 lines whereas gorilla/websocket is at 3500 lines. That's more code to maintain,more code to test, more code to document and more surface area for bugs.

The future of gorilla/websocket is also uncertain. Seegorilla/websocket#370.

Pure conjecture but I would argue that the sprawling API has made it difficult to maintain.

Moreover, nhooyr/websocket has support for newer Go idioms such as context.Context andalso uses net/http's Client and ResponseWriter directly for WebSocket handshakes.gorilla/websocket writes its handshakes to the underlying net.Conn which meansit has to reinvent hooks for TLS and proxying and prevents support of HTTP/2.

Some more advantages of nhooyr/websocket are that it supports concurrent writes and makes itvery easy to close the connection with a status code and reason compared to gorilla/websocket.

In terms of performance, there is no significant difference between the two. Will updatewith benchmarks soon (#75).

https://godoc.org/golang.org/x/net/websocket

Unmaintained and the API does not reflect WebSocket semantics. Should never be used.

Seegolang/go#18152

https://github.com/gobwas/ws

This library has an extremely flexible API but that comes at the cost of usabilityand clarity.

This library is fantastic in terms of performance. The author put in significanteffort to ensure its speed and I have applied as many of its optimizations asI could into nhooyr/websocket. Definitely check out his fantasticblog postabout performant WebSocket servers.

If you want a library that gives you absolute control over everything, this is the library,but for most users, the API provided by nhooyr/websocket will fit better as it is nearly justas performant but much easier to use correctly and idiomatic.