Sam Whited 3e5cd1ed14 websocket: Be explicit about goroutine safety ...

Specifically state that it is safe to call methods on Conn from multiple
goroutines in the docs.

Fixes #6692

Change-Id: I1b0e8812ca5b2e3ca72948c5404d569879e54f34
Reviewed-on: https://go-review.googlesource.com/20455
Reviewed-by: Andrew Gerrand <adg@golang.org>

2016-03-09 02:44:09 +00:00

..

client.go

websocket: fix socket leak in the case of negotiation failure

2015-03-14 03:04:11 +00:00

exampledial_test.go

go.net: use golang.org/x/... import paths

2014-11-10 09:04:43 +11:00

examplehandler_test.go

go.net: use golang.org/x/... import paths

2014-11-10 09:04:43 +11:00

hybi_test.go

websocket: don't send IPv6 zone identifier in outbound request, per RFC 6874

2015-08-13 11:46:27 +00:00

hybi.go

websocket: don't send IPv6 zone identifier in outbound request, per RFC 6874

2015-08-13 11:46:27 +00:00

server.go

websocket: drop unreachable code

2015-08-03 20:45:16 +00:00

websocket_test.go

websocket: handle solicited and unsolicited Ping/Pong frames correctly

2015-08-04 03:35:05 +00:00

websocket.go

websocket: Be explicit about goroutine safety

2016-03-09 02:44:09 +00:00