HTTP
posts (24)
- Realtime in the Browser: From Polling to WebTransport7/7
Polling, Streaming, SSE, WebSocket, or WebTransport?
The choice follows from the traffic model: freshness, direction, frequency, ordering and reliability. The simplest correct mechanism usually wins.
- 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.
- Realtime in the Browser: From Polling to WebTransport5/7
WebSockets: A Persistent Bidirectional Communication Channel
After the handshake there are no requests and responses left, only frames. A persistent connection is state, and it reaches the load balancer, the deploy and…
- Realtime in the Browser: From Polling to WebTransport4/7
Server-Sent Events: An Event Protocol over HTTP Streaming
A standard event format and reconnection on top of an HTTP stream. Last-Event-ID gives you resume, but it does not solve event durability in the system.
- Realtime in the Browser: From Polling to WebTransport3/7
HTTP Streaming: One Response, Many Chunks of Data
A response can be produced over time. A transport chunk is not a message, so framing and backpressure become the application's business.
- Realtime in the Browser: From Polling to WebTransport2/7
Long Polling: When the Server Delays the Response
The server does not answer until it has something to send. What appears is a chain of long requests, where the timeout and the cursor are part of the protocol.
- Realtime in the Browser: From Polling to WebTransport1/7
Polling: Building Realtime with Repeated Requests
The delay is a function of the interval, and the cost is there even when nothing changes. In exchange every request is independent and the whole infrastructure…
- series · 7 parts
Realtime in the Browser: From Polling to WebTransport
Realtime is a requirement about the maximum acceptable delay of information, not the name of a protocol. The mechanisms from polling to WebTransport, each born…
- Ways of Talking to a Backend: From HTML Forms to GraphQL5/6
RPC: When an API Models Operations Instead of Resources
RPC starts from the operation, not the resource. Intent becomes explicit, but the semantics move out of HTTP and into the application contract.
- Ways of Talking to a Backend: From HTML Forms to GraphQL4/6
REST: Resources, Representations, and HTTP Semantics
REST is not "JSON plus endpoints". It is resources identified by URIs, representations kept separate from the resource, and the meaning of HTTP methods put to…