undefined | Better HN

0 pointsstephenr11y ago0 comments

It isn't 2003, IE is not likely to be a majority of visitors any more.

Caniuse.com reports 75% global relative support for EventSource and just 85% for websockets.

To claim that "you can control your stack" as a solution to a protocol that has well known issues with multiple components in the path between a client and the server is somewhat naive frankly.

As for the "pull vs push" debate: event source lets you open a channel to a resource on the server and wait for it to send you data.

XHR long polling works exactly the same way - you open an asynchronous connection and wait for data, the only difference is you need to handle reconnects, and the message parsing is done in user land code rather than in c/whatever.

Long polling is definitely not about making a new xhr request every couple of seconds to check for more data.

0 comments

1 comments · 1 top-level

asergeyev11y ago

There is nothing wrong with server side events. I even played with them already.

But for bi-directional communication we do have to use websockets and it's the good tool for the job.

If you'd like to see maybe event source is something that could be added to websocketd as additional protocol, start conversation in issues, nothing is wrong with pitching an idea. We already got cgi and static html because it's not always about websockets, sometimes you want other things handy.

j / k navigate · click thread line to collapse