4 ms·
Everything 'just works', yet you needed to create your own server for it which needs scripting support? IMO 'just works' means Apache suupports it out of the b
by alt227 2y ago
Everything 'just works', yet you needed to create your own server for it which needs scripting support?
IMO 'just works' means Apache suupports it out of the box with a simple config file and you can just start sending messages to client IPs.
- benwilber0 2y ago"just works" in the sense that this is a complete SSE client application: while true; do curl example.com/sse | handle-messages.sh done Because it's just text-over-http. This isn't possible with websockets without some kind of custom client and layer 7 protocol stack.
- anamexis 2y agoIt’s functional, but I wouldn’t say it’s complete without Last-Event-Id handling.
- deleted 2y ago[deleted]
- Sammi 2y agoYou could do a lobotomized WebSockets implementation that was an extremely thin layer on top of http, similarly to this. In this way SSE and WebSockets are exactly the same. They are HTTP requests that you keep open. To firewalls and other network equipment both look the same. They look like long lived http requests, because that is what they are.