Expand description
RFC 9113 connection/stream framing. Caller retains partial frames and acknowledges writes. DATA is borrowed, flow-control credit is returned explicitly by the host.
Structs§
- Connection
- Frame
- Limits
- Settings
- SETTINGS parameters this endpoint sends: at most one value per identifier,
kept and serialised in ascending identifier order (the order Node writes
them in). An empty
Settingsis a valid, empty SETTINGS frame. - Settings
Frame - The parameters of one SETTINGS frame the peer sent, borrowed from the input exactly as they were on the wire: in frame order, duplicates and unknown identifiers included. RFC 9113 section 6.5.3 processes them in that order, so for a repeated identifier the last value is the one in force.
- Step
- One decode step: how much of
inputwas consumed, and the event it produced, if any. See the step contract.
Enums§
- Event
- Headers
Kind - Which of the three header blocks an
Event::Headerscarries. The connection already enforces the distinction, so a host does not have to trackreceived_headitself to tell them apart. - Role