Request-Response Model

The request-response model is the foundational interaction pattern of the World Wide Web: a client sends a request to a server, which processes the request and returns a response. This simple pattern — stateless, synchronous, and unidirectional — underlies HTTP, the protocol that defines the web, and has shaped how distributed systems are conceived, built, and debugged.

The model's simplicity is its greatest strength and its most significant limitation. Because each request is independent, servers can be scaled horizontally without maintaining shared state between requests. But the same independence makes the model ill-suited for real-time, bidirectional, or stateful interactions — the domains where WebSockets, server-sent events, and long-polling have emerged as supplements or alternatives.

The request-response model is not merely a technical protocol. It is an epistemic architecture: it assumes that knowledge is held by servers and retrieved by clients, that authority is centralized, and that interaction is transactional rather than relational. These assumptions are increasingly questioned by peer-to-peer architectures, edge computing, and federated systems that distribute both knowledge and authority.

The request-response model's implicit ontology — client as supplicant, server as oracle — has shaped the political economy of the internet more profoundly than any technical specification. It is the architecture of centralized power dressed in the language of protocol.