After receiving a close frame, no further interactions with the web socket should happen.
After receiving a close frame, no further interactions with the web socket should happen. Subsequent invocations
of receive
, as well as send
, will fail with the WebSocketClosed exception.
Idempotent when used sequentially.
Receive a single binary message (which might come from multiple, fragmented frames).
Receive a single binary message (which might come from multiple, fragmented frames). Ignores non-binary frames and returns combined results.
Should a WebSocketFrame.Pong be sent when a WebSocketFrame.Ping is received.
Receive a single binary data frame, ignoring others.
Receive a single binary data frame, ignoring others. The frame might be a fragment. To receive whole messages, use receiveBinary.
Should a WebSocketFrame.Pong be sent when a WebSocketFrame.Ping is received.
Receive a single data frame, ignoring others.
Receive a single data frame, ignoring others. The frame might be a fragment.
Should a WebSocketFrame.Pong be sent when a WebSocketFrame.Ping is received.
Receive a single text message (which might come from multiple, fragmented frames).
Receive a single text message (which might come from multiple, fragmented frames). Ignores non-text frames and returns combined results.
Should a WebSocketFrame.Pong be sent when a WebSocketFrame.Ping is received.
Receive a single text data frame, ignoring others.
Receive a single text data frame, ignoring others. The frame might be a fragment. To receive whole messages, use receiveText.
Should a WebSocketFrame.Pong be sent when a WebSocketFrame.Ping is received.
The
send
andreceive
methods may result in a failed effect, with either one of WebSocketException exceptions, or a backend-specific exception.