Hacker News Reader

Interesting difference between Server-Sent Events and Websockets if the former can deliver out-of-order like UDP: "Because SSE works on top of HTTP, HTTP protocol improvements can also benefit SSE. For example, the in-development HTTP/3 protocol, built on top of QUIC, could offer additional performance improvements in the presence of packet loss due to lack of head-of-line blocking."

View on HN

Could any of the downvoters explain why the quoted is an advantage over Websockets then? The quote is from the README section "Why Server Sent Events (SSE)? Why would you choose SSE over WebSockets?": https://github.com/unifrost/unifrost/blob/master/README.md#w...

SSE can deliver out of order? Is that within a single EventSource or across multiple. I thought that within a single EventSource all messages were in order.

Good point and a downer if you need to hack with multiple EventSources. In any case, I see there's ongoing standardisation work on WebTransport including a DatagramTransport on top of QUIC: "It can be used like WebSockets but with support for multiple streams, unidirectional streams, out-of-order delivery, and reliable as well as unreliable transport." https://wicg.github.io/web-transport/#introduction

Reply on news.ycombinator.com