liveBook · Manning

HTTP

As explained in Vanilla Web

The application-layer protocol used to transfer resources and messages between web clients and servers.

HTTP is the protocol a web client uses to exchange resources and messages with a server. A browser interface can communicate with HTTP endpoints directly, without adopting a framework-specific client–server contract. The server can connect those requests to backend logic implemented in any suitable technology. section 1.2 section 1.3

When an interface works with remote data, keep the responsibilities separate:

  • Use HTTP to fetch, send, or stream data. section 12.0
  • Represent the request lifecycle as explicit UI states. section 12.0
  • Decide separately whether received data needs client-side caching or persistence. section 12.0

HTTP is the primary route for communication with the backend here, not the only possible channel. WebSockets and other network protocols can serve different communication needs. section 1.3 section 12.0

How Vanilla Web covers it

How deep it goes
Identifies HTTP’s place in the web stack and its data-transfer roles, without detailing request syntax or protocol internals.
Examples
Uses fetching, sending, and streaming application data as concrete HTTP tasks.
What it assumes
Places HTTP alongside frontend technologies while leaving the choice of backend language open.
What you can do after
Evaluate/understand HTTP’s role in moving data between a browser interface and a backend.
How it connects
Links HTTP to browser APIs, backend APIs, request lifecycle UI states, client-side caching, and WebSockets.

Also explained in

Compare how 11 books explain HTTP →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Vanilla Web. The section links point to the parts of the book it draws on.