Hacker News new | ask | show | jobs
by realPubkey 546 days ago
Yes most servers support websockets. But unfortunately most proxies and firewalls do not, especially in big company networks. Suggesting my users to use SSEs for my database replication stream solved most of their problems. Also setting up a SSE endpoint is like 5 lines of code. WebSockets instead require much more and you also have to do things like pings etc to ensure that it automatically reconnects. SEEs with the JavaScript EventSource API have all you need build in:

https://rxdb.info/articles/websockets-sse-polling-webrtc-web...
2 comments
the_mitsuhiko 546 days ago
SSE also works well on HTTP/3 whereas web sockets still don’t.
link
apitman 546 days ago
I don't see much point in WebSockets for HTTP/3. WebTransport will cover everything you would need it for an more.
link
the_mitsuhiko 546 days ago
That might very well be but the future is not today.
link
apitman 546 days ago
But why add it to HTTP/3 at all? HTTP/1.1 hijacking is a pretty simple process. I suspect HTTP/3 would be significantly more complicated. I'm not sure that effort is worth it when WebTransport will make it obselete.
link
the_mitsuhiko 546 days ago
It was added to HTTP/2 as well and there is an RFC. (Though a lot of servers don’t support it even on HTTP/2)

My point is mostly that SSE works well and is supported and that has A meaningful benefit today.

link
leni536 546 days ago
To have multiple independent websocket streams, without ordering requirements between streams.
link
deaf_coder 545 days ago
going slightly off the tangent here, does FaaS cloud providers like AWS, CloudFlare, and etc support SSEs?

Last time I checked, they don't really support it.

link