4 ms·
I didn't know that SSE came first, thanks for adding that context. It does feel like websockets tried to cram several novel features whereas SSE was simply giv
by klabb3 5y ago
I didn't know that SSE came first, thanks for adding that context.
It does feel like websockets tried to cram several novel features whereas SSE was simply giving proper clothing to the existing art of long polling.
In particular, WS is binary encoded, has support for multiplexing/message splitting, several optional http headers, which in hindsight appears to have simply complicated the spec at little-to-nil value.