3 ms·
Good point! We did consider SSE, but ultimately decided against it due to the way we have to re-implement response payloads (one for application/json and one fo
by lunarcave 2y ago
Good point! We did consider SSE, but ultimately decided against it due to the way we have to re-implement response payloads (one for application/json and one for text/event-stream).
I've not personally witnessed this, but people on the internets have said that _some_ proxies/LBs have problems with SSE due to the way it does buffering.
- gorjusborg 2y ago> we have to re-implement response payloads (one for application/json and one for text/event-stream) I am curious about what you mean here. The 'text/event-stream' allows for abitrary event formats, it just provides structure for EventSource to be able to parse. You should only need one 'text/event-stream' and should be able send the same JSON via normal or SSE response.
- josephg 2y agoWhat the GP commenter might have meant is that websockets support binary message bodies. SSE does not.