multiplexing
Carrying many independent conversations over one connection at the same time by interleaving their pieces.
In more detail
HTTP/2 and HTTP/3 multiplex many requests on one connection, so a slow response no longer blocks the others the way it does in HTTP/1.1. It saves opening many connections, each with its own set-up cost.
Related terms
- HTTP/2 — A version of HTTP that sends the same methods, statuses and headers in a binary format and runs many requests at once over one connection.
- HTTP/3 — The newest version of HTTP, which keeps the meaning of HTTP/2 but runs over QUIC on UDP instead of TCP.
- framing — The rule that marks where one message or record ends and the next begins in a stream of bytes.
- head-of-line blocking — A delay where one slow or lost item at the front of a queue holds up everything behind it.
- HTTP/2 stream — One request and its response inside an HTTP/2 connection, identified by a stream number and carried as a sequence of frames.
Taught in
- What An API Is, And The Alternatives — Modern API Architecture: REST, GraphQL & gRPC
- Native HTTP/2 Protocols: Multiplexed Streams & Push — Node.js Internals & Backend Services