Multiplexed streams
02Frames for several exchanges share a connection, with stream identifiers keeping their state separate.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 5 ↗
RFC 9113 · § 5EXAMPLE
3 / 3
03
Complete independently
END_STREAM closes one sending direction without closing unrelated streams.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
A stream is a bidirectional frame sequence; stream 0 is connection control.
- A stream is a bidirectional frame sequence; stream 0 is connection control.
- Client-initiated streams use odd identifiers; server-initiated streams use even identifiers.
- Multiplexing does not eliminate TCP head-of-line blocking.
Examples are illustrative. Consult the linked RFC and its errata for implementation details.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy