LongPolling

The client makes a request and the server holds it open until there's new data (or a timeout), then the client immediately re-requests — near-real-time without a persistent connection.

Why we need this / what value this brings

Delivers near-real-time updates without requiring WebSocket/SSE infrastructure support — works anywhere plain HTTP does.

When to use this

Only when SSE/WebSockets genuinely aren't an option (very old client support requirements, infra that can't hold persistent connections) — otherwise SSE is simpler and more efficient.

How to use or implement this

If ever needed: hold the request open server-side until new data or a timeout, then have the client immediately re-issue the request on response.

Research questions

• Before WebSockets/SSE were widely supported, this was the standard workaround — is it ever still the right choice today, or purely legacy knowledge?

---

Empty folder — drop notes, links, and findings here as you research.