ServerSentEvents

One-way (server → client) persistent stream over plain HTTP — simpler than WebSockets when the client never needs to push data back over the same connection.

Why we need this / what value this brings

Gets most of WebSockets' real-time feel with plain HTTP (works through normal proxies/load balancers, simpler server implementation) when you only need one-directional server-to-client push.

When to use this

Streaming responses where the client never needs to send anything back over the same connection — LLM token streaming, live progress updates, live status feeds.

How to use or implement this

Use the standard EventSource API on the client (built-in reconnect) and stream text/event-stream responses from the server; fall back to WebSockets only if the client also needs to push data back.

Research questions

• This is what streaming LLM tokens to the browser (AI/LLMIntegration) typically uses — why is SSE a better fit than WebSockets for that specific case?
• SSE auto-reconnects natively in the browser (EventSource) — what does that save you compared to hand-rolling WebSocket reconnect logic?

---

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