Enum embedded_websocket::framer_async::ReadResult

pub enum ReadResult<'a> {
    Binary(&'a [u8]),
    Text(&'a str),
    Pong(&'a [u8]),
    Ping(&'a [u8]),
    Close(CloseMessage<'a>),
}

Variants

Binary(&'a [u8])

Text(&'a str)

Pong(&'a [u8])

We received a pong message in response to a ping message we sent earlier. This should contain the same data as was sent in the ping message

Ping(&'a [u8])

We received a ping message from the other end A pong message with the same content will automatically be sent back as per the websocket spec However, this message is exposed to you so that you can see what is in the ping message

Close(CloseMessage<'a>)

The other end initiated a close handshake. The contents of this message is usually the reason for the close A close response message will automatically be sent back to the other end to complete the close handshake However, this message is exposed to you so that you can see why