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










