Hi Hacker News,
I was experimenting with HTML SSE (alternative to web socktets), and made a fun Apple TV party game in the process. It turned out to be great for my situation (where you need to do realtime synchronization from server to client(s) but web sockets were overkill).<p>You can check out the game here:
<a href="https://electrollama.net/alphaparty" rel="nofollow">https://electrollama.net/alphaparty</a><p>I wrote a post about configuring Nginx to work with SSE when used as a reverse proxy for node (this was a bit tricky... my server worked fine when connecting straight to node, but not through a proxy without some monkeying around)
<a href="https://www.electrollama.net/blog/2017/6/22/html-sse-with-nodejs-and-nginx" rel="nofollow">https://www.electrollama.net/blog/2017/6/22/html-sse-with-no...</a><p>Also, my first post on HN, despite being a lurker here for over 5 years! I apologize if I've formatted this wrong...
It's good to see someone making use of SSE/EventSource. so many devs just jump on the web sockets bandwagon when all they need is one way data flow with maybe occasional data sent from the client, which imo works better using sse and xhr when required.<p>A key thing to me is that sse can be polyfilled for older browsers. Websockets cannot.