SSE: uses a standard HTTP response with Content-Type: text/event-stream that stays open, letting the server push events to the browser. The EventSource API consumes it on the client.
2 / 5
A key limitation of SSE compared to WebSockets is that it is what?
Unidirectional: SSE only flows server to client. For client-to-server messages you still use normal HTTP requests. WebSockets, by contrast, are full-duplex.
3 / 5
What useful built-in feature does SSE provide for dropped connections?
Auto-reconnect:EventSource reconnects automatically and sends the Last-Event-ID header so the server can resume from where the client left off, simplifying resilient streaming.
4 / 5
Why is SSE often simpler to deploy than WebSockets?
HTTP compatibility: because SSE is just an HTTP response, it passes through standard load balancers, proxies, and firewalls and benefits from HTTP/2 multiplexing, unlike the protocol upgrade WebSockets require.
5 / 5
SSE is a good fit for which use case?
SSE use case: one-way streams like live scores, stock tickers, notifications, or progress updates fit perfectly. For interactive two-way needs (chat, gaming), WebSockets are the better choice.