Hacker News Reader

Going off my personal experience I don't see SSE being mentioned anywhere at all. But I always come across some new shiny web framework/wsgi listing websockets as a feature.

The reality is a lot of applications simply do not need bi-directional client-server communication but for some reason this abuse has been adopted as standard.

View on HN

> The reality is a lot of applications simply do not need bi-directional client-server communication but for some reason this abuse has been adopted as standard.

I suspect the treatment as 'standard' is what thread OP is talking about. See my sibling comment in the thread. Unless you absolutely need websocket, SSE is simpler, and due to that, better.

I suspect the reason many select websocket over SSE is due to its limitations (connection limit under HTTP/1.1, no client->server sends), but SSE for server->client events and normal HTTP requests for state fetching is better architecturally for bog standard apps in my experience.

Reply on news.ycombinator.com