Specification for Server Sent Events / SSE

Hi everyone,

not sure if this has been discussed already. I recently stumbled over SSE. https://en.wikipedia.org/wiki/Server-sent_events (coming from https://htmx.org/attributes/hx-sse/).

Right now it’s hard to differentiate SSE since it identifies itself as scope["type"] == "http".

Would it be possible to define scope["type"] == "sse"?

At least when considering Django, regular StreamingResponses are not a stable solution. async/await feels much better when coping with these kind of web requests (long living connections).

Best Sven

[andrewgodwin]

To answer the overall idea of this issue - there’s not really a sensible way we can separate SSE into a separate spec. It’s literally just a different way of doing streaming HTTP responses, and as such, should live under HTTP (unlike WebSockets, which are their own binary protocol).

Could there be a nice third-party library that made composing the responses easier? Absolutely. Is this something we can help at the spec level? Not really, since that would require all servers to write and compose code just for this case - a case that’s already covered with the spec anyway.

[abersheeran]

By the way, I don’t think it’s a good idea to separate SSE. It is also just a normal HTTP response.