A single item in a Stream.
A generic HTTP2 message.
Request messages include helpers for accessing pseudo-headers.
A Stream represents a stream of Data frames, optionally followed by Trailers.
A Stream represents a stream of Data frames, optionally followed by Trailers.
A Stream is not prescriptive as to how data is produced. However, flow control semantics are built into the Stream--consumers MUST release each data frame after it has processed its contents.
Consumers SHOULD call read()
until it fails (i.e. when the
stream is fully closed).
If a consumer cancels a read()
Future, the stream is reset.
When an exception is encountered in a stream, it is wrapepd in a StreamError to indicate whether the error originated from the remote (network) or local (application) side of the stream.
A generic HTTP2 message.
The message itself includes the Headers that initiated the message (comprising all HEADERS frames sent to initiate the message).
Furthermore, messages have an (optional) Stream of data and trailer frames.
These types are only intended to satisfy session layer concerned and are not intended to provide a rish programming interface. However, it is hoped that other types may be built upon / adapated to satisfy a broader set of use cases.