1
0
mirror of https://github.com/beego/bee.git synced 2024-11-18 08:40:54 +00:00
bee/vendor/github.com/gorilla/websocket
2017-03-17 13:33:15 +08:00
..
AUTHORS Add gorilla/websocket to vendor folder 2017-01-23 20:12:40 +01:00
client_clone_legacy.go cleanup 2017-03-17 13:33:15 +08:00
client_clone.go cleanup 2017-03-17 13:33:15 +08:00
client.go cleanup 2017-03-17 13:33:15 +08:00
compression.go cleanup 2017-03-17 13:33:15 +08:00
conn_read_legacy.go Add gorilla/websocket to vendor folder 2017-01-23 20:12:40 +01:00
conn_read.go Add gorilla/websocket to vendor folder 2017-01-23 20:12:40 +01:00
conn.go cleanup 2017-03-17 13:33:15 +08:00
doc.go cleanup 2017-03-17 13:33:15 +08:00
json.go Add gorilla/websocket to vendor folder 2017-01-23 20:12:40 +01:00
LICENSE Add gorilla/websocket to vendor folder 2017-01-23 20:12:40 +01:00
mask_safe.go cleanup 2017-03-17 13:33:15 +08:00
mask.go cleanup 2017-03-17 13:33:15 +08:00
prepared.go cleanup 2017-03-17 13:33:15 +08:00
README.md cleanup 2017-03-17 13:33:15 +08:00
server.go cleanup 2017-03-17 13:33:15 +08:00
util.go Add gorilla/websocket to vendor folder 2017-01-23 20:12:40 +01:00

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.