liveBook · Manning

Push-based update

As explained in The Art of Code

A communication technique in which a server sends update data to clients when relevant changes occur.

Push-based update is a communication technique in which the server sends data when something meaningful changes, instead of waiting for repeated client requests. section 8.4.4

Polling versus push

A dashboard that polls every five seconds repeatedly asks whether anything changed, creating many wasted requests. When updates are frequent, WebSockets or Server-Sent Events can send changes only when needed. section 8.4.4

Choose push when frequent updates justify an open connection; choose modest polling when updates are rare and simplicity matters. Open connections still consume server resources. section 8.4.4

How The Art of Code covers it

How deep it goes
Compares polling and push mechanisms, explains their efficiency tradeoffs, and stops short of implementation details.
Examples
Uses dashboards refreshing weather or financial data to contrast repeated polling with event-driven delivery.
What it assumes
Assumes familiarity with clients, servers, endpoints, and network requests while defining polling from the comparison.
What you can do after
Evaluate whether polling or push better fits update frequency, simplicity needs, and server-resource constraints.
How it connects
Connects push-based updates with polling, WebSockets, Server-Sent Events, HTTP caching, and offline-first design.

Related concepts

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