https://github.com/gorilla/websocket.git

Kamil Kisiel c17c80cb48 Merge pull request #385 from dottyjones/master		7 years ago
examples	cd94665a65 Minor fixes in comments	7 years ago
.gitignore	6656ddce91 add newline and remove extra space	7 years ago
.travis.yml	f37d158860 Travis config: add Go 1.10.x, revert 1.4.x to 1.4	7 years ago
AUTHORS	15aed3b4a4 Relicense to the Gorilla WebSocket Authors.	11 years ago
LICENSE	15aed3b4a4 Relicense to the Gorilla WebSocket Authors.	11 years ago
README.md	6656ddce91 add newline and remove extra space	7 years ago
client.go	21ab95fa12 Modify headers to match case used in RFC examples	7 years ago
client_clone.go	3f3e394da2 Update cloneTLSConfig to use Go 1.8 Config.Clone method	8 years ago
client_clone_legacy.go	3f3e394da2 Update cloneTLSConfig to use Go 1.8 Config.Clone method	8 years ago
client_server_test.go	badcf87185 Improve names in handshake deadline test	7 years ago
client_test.go	71fa72d484 Replace parseURL() with net/url.Parse() (#290)	8 years ago
compression.go	eb457539f7 fix flate write pool size to work with best compression	8 years ago
compression_test.go	b0dc45572b Change default and add API for compression level	9 years ago
conn.go	eb92580837 Use net.Buffers to write multiple slices to connection	7 years ago
conn_broadcast_test.go	804cb600d0 Prepared Messages (#211)	8 years ago
conn_read.go	be01041b66 Reduce memory allocations in NextReader, NextWriter	9 years ago
conn_read_legacy.go	be01041b66 Reduce memory allocations in NextReader, NextWriter	9 years ago
conn_test.go	23059f2957 Update with gofmt on tip	8 years ago
conn_write.go	eb92580837 Use net.Buffers to write multiple slices to connection	7 years ago
conn_write_legacy.go	eb92580837 Use net.Buffers to write multiple slices to connection	7 years ago
doc.go	91f589db02 Improve check origin documentation	7 years ago
example_test.go	d1d4086b14 Fix go vet warning	9 years ago
json.go	92f772e4b3 Misc cleanup	8 years ago
json_test.go	b6ab76f1fe Provide all close frame data to application	10 years ago
mask.go	23059f2957 Update with gofmt on tip	8 years ago
mask_safe.go	adf16b3178 Add safe maskBytes	9 years ago
mask_test.go	adf16b3178 Add safe maskBytes	9 years ago
prepared.go	804cb600d0 Prepared Messages (#211)	8 years ago
prepared_test.go	804cb600d0 Prepared Messages (#211)	8 years ago
proxy.go	cd94665a65 Minor fixes in comments	7 years ago
server.go	21ab95fa12 Modify headers to match case used in RFC examples	7 years ago
server_test.go	b648f206c2 Use ASCII case folding in same origin test	8 years ago
util.go	23059f2957 Update with gofmt on tip	8 years ago
util_test.go	c55883f973 Add parseExtensions test case (#310)	8 years ago
x_net_proxy.go	b89020ee79 Add SOCKS5 support	8 years ago

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

Gorilla WebSocket compared with other packages

Notes:

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

	github.com/gorilla	golang.org/x/net
RFC 6455 Features
Passes Autobahn Test Suite	Yes	No
Receive fragmented message	Yes	No, see note 1
Send close message	Yes	No
Send pings and receive pongs	Yes	No
Get the type of a received data message	Yes	Yes, see note 2
Other Features
Compression Extensions	Experimental	No
Read message using io.Reader	Yes	No, see note 3
Write message using io.WriteCloser	Yes	No, see note 3

README.md