You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
k3s/vendor/github.com/gorilla/websocket
Darren Shepherd d246c89254
go mod vendor
5 years ago
..
.gitignore go mod vendor 5 years ago
.travis.yml go mod vendor 5 years ago
AUTHORS go mod vendor 5 years ago
LICENSE Update vendor 6 years ago
README.md go mod vendor 5 years ago
client.go go mod vendor 5 years ago
client_clone.go Update vendor 6 years ago
client_clone_legacy.go Update vendor 6 years ago
compression.go Update vendor 6 years ago
conn.go go mod vendor 5 years ago
conn_write.go go mod vendor 5 years ago
conn_write_legacy.go go mod vendor 5 years ago
doc.go go mod vendor 5 years ago
json.go go mod vendor 5 years ago
mask.go go mod vendor 5 years ago
mask_safe.go Update vendor 6 years ago
prepared.go go mod vendor 5 years ago
proxy.go go mod vendor 5 years ago
server.go go mod vendor 5 years ago
trace.go go mod vendor 5 years ago
trace_17.go go mod vendor 5 years ago
util.go go mod vendor 5 years ago
x_net_proxy.go go mod vendor 5 years ago

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.