Build a response which will accept an HTTP websocket upgrade request and initiate a websocket connection using the supplied exchange to process and respond to websocket messages.
- Value Params
- headers
Handshake response headers, such as such as:Sec-WebSocket-Protocol.
- onHandshakeFailure
The status code to return when failing to handle a websocket HTTP request to this route. default: BadRequest
- onNonWebSocketRequest
The status code to return to a client making a non-websocket HTTP request to this route. default: NotImplemented
- Companion
- object
Value members
Concrete methods
- Value Params
- sendReceive
The send-receive stream represents transforming of incoming messages to outgoing for a single websocket Once the stream have terminated, the server will initiate a close of the websocket connection. As defined in the websocket specification, this means the server will send a CloseFrame to the client and wait for a CloseFrame in response before closing the connection, this ensures that no messages are lost in flight. The server will shutdown the connection when it receives the
CloseFramemessage back from the client. The connection will also be closed if the client does not respond with aCloseFrameafter some reasonable amount of time. Another way of closing the connection is by emitting aCloseFramein the stream of messages heading to the client. This method allows one to attach a message to theCloseFrameas defined by the websocket protocol. Unfortunately the current implementation does not quite respect the description above, it violates the websocket protocol by terminating the connection immediately upon reception of aCloseFrame. This bug will be addressed soon in an upcoming release and this message will be removed. Currently, there is no way for the server to be notified when the connection is closed, neither in the case of a normal disconnection such as a Close handshake or due to a connection error. There are plans to address this limitation in the future.
- Value Params
- receive
The receive side of the Exchange is a sink to which the framework will push the incoming websocket messages Once both streams have terminated, the server will initiate a close of the websocket connection. As defined in the websocket specification, this means the server will send a CloseFrame to the client and wait for a CloseFrame in response before closing the connection, this ensures that no messages are lost in flight. The server will shutdown the connection when it receives the
CloseFramemessage back from the client. The connection will also be closed if the client does not respond with aCloseFrameafter some reasonable amount of time. Another way of closing the connection is by emitting aCloseFramein the stream of messages heading to the client. This method allows one to attach a message to theCloseFrameas defined by the websocket protocol. Unfortunately the current implementation does not quite respect the description above, it violates the websocket protocol by terminating the connection immediately upon reception of aCloseFrame. This bug will be addressed soon in an upcoming release and this message will be removed. Currently, there is no way for the server to be notified when the connection is closed, neither in the case of a normal disconnection such as a Close handshake or due to a connection error. There are plans to address this limitation in the future.- send
The send side of the Exchange represents the outgoing stream of messages that should be sent to the client