k3s/vendor/github.com/gorilla/websocket
Darren Shepherd fa08d6076c Update vendor 2019-01-11 21:58:27 -07:00
..
.gitignore Update vendor 2019-01-11 21:58:27 -07:00
.travis.yml Update vendor 2019-01-11 21:58:27 -07:00
AUTHORS Update vendor 2019-01-11 21:58:27 -07:00
LICENSE Update vendor 2019-01-11 21:58:27 -07:00
README.md Update vendor 2019-01-11 21:58:27 -07:00
client.go Update vendor 2019-01-11 21:58:27 -07:00
client_clone.go Update vendor 2019-01-11 21:58:27 -07:00
client_clone_legacy.go Update vendor 2019-01-11 21:58:27 -07:00
compression.go Update vendor 2019-01-11 21:58:27 -07:00
conn.go Update vendor 2019-01-11 21:58:27 -07:00
conn_read.go Update vendor 2019-01-11 21:58:27 -07:00
conn_read_legacy.go Update vendor 2019-01-11 21:58:27 -07:00
doc.go Update vendor 2019-01-11 21:58:27 -07:00
json.go Update vendor 2019-01-11 21:58:27 -07:00
mask.go Update vendor 2019-01-11 21:58:27 -07:00
mask_safe.go Update vendor 2019-01-11 21:58:27 -07:00
prepared.go Update vendor 2019-01-11 21:58:27 -07:00
server.go Update vendor 2019-01-11 21:58:27 -07:00
util.go Update vendor 2019-01-11 21:58:27 -07:00

README.md

Gorilla WebSocket

Gorilla WebSocket is a Go implementation of the WebSocket protocol.

Build Status GoDoc

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 Test Suite using the application in the examples/autobahn subdirectory.

Gorilla WebSocket compared with other packages

github.com/gorilla golang.org/x/net
RFC 6455 Features
Passes Autobahn Test SuiteYesNo
Receive fragmented messageYesNo, see note 1
Send close messageYesNo
Send pings and receive pongsYesNo
Get the type of a received data messageYesYes, see note 2
Other Features
Compression ExtensionsExperimentalNo
Read message using io.ReaderYesNo, see note 3
Write message using io.WriteCloserYesNo, see note 3

Notes:

  1. Large messages are fragmented in Chrome's new WebSocket implementation.
  2. The application can get the type of a received data message by implementing a Codec marshal function.
  3. 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.