brainkim
Reputation: 991
What is the difference between WebSocket `closing` vs `closed` readyState?
WebSocket.readyState can be CONNECTING, OPEN, CLOSING or CLOSED. What is the difference between CLOSING and CLOSED states? Why is it useful to distinguish between these two states? Can I treat a CLOSING websocket the same as a CLOSED websocket?
Upvotes: 0
Views: 389
Answers (1)
Remy Lebeau
Reputation: 597285
In the CLOSING state, the WebSocket has sent a Close packet to the peer indicating that the connection is being intentionally ended and why, and is awaiting a reply from the peer. The TCP connection is still open at this stage.
In the CLOSED state, the TCP connection has been closed, or was not successfully opened to begin with.
Upvotes: 1
Related Questions
- What does "WebSocket is closed before the connection is established" mean?
- Does the connection get closed at any point during the WebSocket handshake or immediately after?
- Closing WebSocket correctly (HTML5, Javascript)
- When is it preferable to use ws.terminate() VS ws.close()
- .net WebSocket: CloseOutputAsync vs CloseAsync
- Where to catch "WebSocket is already in CLOSING or CLOSED state." message
- WebSocket: call close() won't trigger onclose handler?
- Synchronous closing websocket in browser
- What's the difference between end() and close() in io.vertx.core.http.impl.WebSocketImplBase?
- How to ensure that readyState of a WebSocket has turned to CLOSED (3)?