An adapter from CIO low-level headers map to ktor Headers interface

Represents a multipart data object that does parse and convert parts to ktor's PartData

Websocket close reason

Represents a parsed Connection header

Decoder job type

Default websocket session with ping-pong and timeout processing and built-in closeReason population

Default web socket session implementation that handles ping-pongs, close sequence and frame fragmentation

Encoder job type

A frame received or ready to be sent. It is not reusable and not thread-safe

Frame types enum

A headers map data structure used in CIO

Represents a base HTTP message type for request and response

HTTP request handler function

Represents a multipart content starting event. Every part need to be completely consumed or released via release

Represents a text range with mutable bounds

An HTTP parser exception

Represents a RAW web socket session

Represents an HTTP request

Builds an HTTP request or response

Represents an HTTP response

It provides ability to cancel jobs and schedule coroutine with timeout. Unlike regular withTimeout this implementation is never scheduling timer tasks but only checks for current time. This makes timeout measurement much cheaper and doesn't require any watchdog thread.

API marked with this annotation is internal and not intended to be used outside of ktor It is not recommended to use it as it may be changed in the future without notice or it may be too low-level so could damage your data.

Class that continuously reads a byteChannel and converts into Websocket Frame exposing them in incoming.

Represents a web socket session between two peers

Class that processes written outgoing Websocket Frame, serializes them and writes the bits into the writeChannel.