mirror of https://github.com/gorilla/websocket.git
df94ef6daa
- Revert back to using Subprotocols []string. The protocol negotiation using Subprotocols should meet the needs of most applications. Applications are not locked into using this negotiation. An application can pick a protocol some other way and specify the protocol using the Sec-Websocket-Protocol response header. - Parse the origin using url.Parse. This is the correct function to use when parsing a full URL. - Improve comments. |
||
|---|---|---|
| examples | ||
| .gitignore | ||
| .travis.yml | ||
| AUTHORS | ||
| LICENSE | ||
| README.md | ||
| client.go | ||
| client_server_test.go | ||
| conn.go | ||
| conn_test.go | ||
| doc.go | ||
| json.go | ||
| json_test.go | ||
| server.go | ||
| server_test.go | ||
| util.go | ||
README.md
Gorilla WebSocket
Gorilla WebSocket is a Go implementation of the WebSocket protocol.
Documentation
Status
The Gorilla WebSocket package provides a complete and tested implementation of the WebSocket protocol. The package API is stable.
Installation
go get github.com/gorilla/websocket
Protocol Compliance
The Gorilla WebSocket package passes the server tests in the Autobahn WebSockets Test Suite using the application in the examples/autobahn subdirectory.
Gorilla WebSocket compared with other packages
| gorilla | go.net | |
|---|---|---|
| Protocol support | RFC 6455 | RFC 6455, see notes |
| Limit size of received message | Yes | No |
| Send pings and receive pongs | Yes | No |
| Send close message | Yes | No |
| Read message using io.Reader | Yes | No, see notes |
| Write message using io.WriteCloser | Yes | No, see notes |
| Encode, decode JSON message | Yes | Yes |
Notes:
- The go.net package does not handle fragmented messages.
- The go.net io.Reader and io.Writer operate across WebSocket frame boundaries. Read returns when the input buffer is full or a frame boundary is encountered, Each call to Write sends a single frame message. The Gorilla io.Reader and io.WriteCloser operate on a single WebSocket message.