Streams
posts (4)
- The Layers of HTTP in the Browser: From fetch() to QUIC7/9
HTTP/2: Multiplexing Changed the Frontend Network Model
The same HTTP semantics, a different wire format. Many parallel requests do not mean many sockets, and stream independence ends at TCP.
- The Layers of HTTP in the Browser: From fetch() to QUIC3/9
Headers and Body: Metadata vs Representation
A body is bytes, not JSON. Headers say how to read it and steer caching, cookies and CORS, even though the application does not fully control them.
- Realtime in the Browser: From Polling to WebTransport6/7
WebTransport: Streams and Datagrams for Realtime over HTTP/3
HTTP/3 and QUIC give a single session many independent streams plus datagrams. Not all data has to arrive reliably and in order.
- Ways of Talking to a Backend: From HTML Forms to GraphQL3/6
Fetch API: The Modern Browser Interface to HTTP
fetch did not change the communication model, only the interface. Request and Response are objects, the body is a stream, and a 404 is not an error.