- https://github.com/gorilla/websocket
- stars:
- 19.1k
- archived
- BSD-2-Clause license
- releases:
- 8
- 2022/01/04 1.5.0
- contributors:
- 74
- stars:
- https://github.com/nhooyr/websocket
- stars:
- 2.9k
- releases:
- 33
- 2021/04/08 1.8.7
- 2020/05/10 1.8.6
- contributors:
- 9
- full context support
- MIT license
- stars:
- https://github.com/gobwas/ws
- stars:
- 5.4k
- releases:
- 14
- 2023/05/xx 1.3.0
- 2023/04/04 1.2.0
- 2021/07/11 1.1.0
- contributors:
- 18
- it fixes 'read timeout' problem
- MIT license
- stars:
- https://pkg.go.dev/golang.org/x/net/websocket
- one of the sub-repositories
- but it's deprecated ?
- BSD-3-Clause
x/net | gorilla | nhooyr | gobwas | |
---|---|---|---|---|
maintained? | ×? | × | ○ | ○ |
stars | - | 19.1k | 2.9k | 5.4k |
releases | ? | 2022/01/04 | 2021/04/08 | 2023/04/04 |
version | 0.9.0? | 1.5.0 | 1.8.7 | 1.2.0 |
contributors | - | 74 | 9 | 18 |
License | BSD-3 | BSD-2 | MIT | MIT |
Feat
(ref: websocket#comparison(@nhooyr))
x/net | gorilla | nhooyr | gobwas | |
---|---|---|---|---|
context (rw) | × | × | ○ | × |
connection alive when deadline (set deadilne) |
○ | × | × | ○ |
- if the deadline exceeded, the entire "tcp" connection is destroyed.
- not only the read (write) connection
- gorilla
- nhooyr
- not only the read (write) connection
- why the behavior of "read timeout" is different?
- MASK in websocket ?
- epoll ?
- gobwas author's blog post
- websocket#comparison(@nhooyr)