-
- Downloads
Implement complete close handshake
I changed my mind after #103 as browsers include a wasClean event to indicate whether the connection was closed cleanly. From my tests, if a server using this library prior to this commit initiates the close handshake, wasClean will be false for the browser as the connection was closed before it could respond with a close frame. Thus, I believe it's necessary to fully implement the close handshake. @stephenyama You'll enjoy this.
Showing
- conn.go 81 additions, 23 deletionsconn.go
- conn_common.go 4 additions, 0 deletionsconn_common.go
- conn_test.go 9 additions, 0 deletionsconn_test.go
- go.mod 1 addition, 0 deletionsgo.mod
- websocket_js.go 35 additions, 13 deletionswebsocket_js.go
- websocket_js_export_test.go 0 additions, 17 deletionswebsocket_js_export_test.go
- websocket_js_test.go 0 additions, 5 deletionswebsocket_js_test.go
... | ... | @@ -21,5 +21,6 @@ require ( |
golang.org/x/sys v0.0.0-20190927073244-c990c680b611 // indirect | ||
golang.org/x/time v0.0.0-20190308202827-9d24e82272b4 | ||
golang.org/x/tools v0.0.0-20190920225731-5eefd052ad72 | ||
golang.org/x/xerrors v0.0.0-20190717185122-a985d3407aa7 | ||
gopkg.in/check.v1 v1.0.0-20180628173108-788fd7840127 // indirect | ||
) |
websocket_js_export_test.go
deleted
100644 → 0
Please register or sign in to comment