SSE transport

[gedw99]

Would be nice and lightweight.

Can do 120 FPS updates when using SSE in browser.
Easy to cluster and firewell and proxy. there is nothing to do as its just HTTP.
Perf due to using HTTP 1, 2 or 3.
Easy LB. Proxies will LB it automatically.
Browsers auto reconnect. nothing to do.

Can be done to be directional based on fetch and EventSource primitives.

---

I am seeing this come up a lot in systems now, and there are many implementations.

The ServerSentEventGenerator must use a response controller that has the following response headers set by default:

Cache-Control = nocache
Connection = keep-alive
Content-Type = text/event-stream

Then the created response should flush immediately to avoid timeouts while 0-♾️ events are created
Multiple calls using ServerSentEventGenerator should be single threaded to guarantee order.

[gedw99]

No response so closing