4 ms·
It's funny that the article says "This enables server sent events" without actually referring to the HTML5 Server Sent Events API: http://www.html5rocks.com/en
by pornel 13y ago
It's funny that the article says "This enables server sent events" without actually referring to the HTML5 Server Sent Events API:
http://www.html5rocks.com/en/tutorials/eventsource/basics/ http://www.html5rocks.com/en/tutorials/eventsource/basics/
SSE is realtime server->client protocol that's fully compatible with HTTP and has lower handshake overhead (no Upgrade roundtrip, doesn't require HTTPS to go through proxies).
- rch 13y agoAgreed. Both approaches have their place, but I see SSE getting overlooked too often.
- yogo 13y agoI'm not 100% up to speed on SSE but since there is no way to "push" to a client isn't it just some form of polling at the end of the day? It's also not supported by IE yet: http://caniuse.com/eventsource http://caniuse.com/eventsource Compare with http://caniuse.com/websockets http://caniuse.com/websockets
- rch 13y agoThat's in keeping with how I think of it: open connection from the client with some reasonable expectations set around e.g. reconnection behavior. Looks like Chrome and Firefox have had support for quite some time. I'm alright with that.
- sampk 13y agoIE is just trying to look all hip and cool and EventSource hasn't generated much hype so it doesn't get implemented.. shame.
- dspillett 13y ago> isn't it just some form of polling at the end of the day? Probably long-poll, a single connection from client to server kept alive with the occasional byte sent one way which sends the message and disconnects when there is something to send (the disconnect, requiring a new request from the client is because some clients won't process what has been sent immediately unless the connection is closed). I once wrote a messaging client that operated this way. It is efficient in terms of bandwidth use and client footprint, though if you are using a process based we server it can be quite inefficient there (an event driven service on few processes/threads is far more efficient for handling many long-lived low-activity connections).
- jessaustin 13y agoThanks for the pointer! This seems much more straightforward than websockets.
- lostcolony 13y agoDo SSEs now support CORS? I know when writing a webapp at the start of this year we went with Websockets because we needed to work in a cross domain environment and SSEs didn't support it; I know it was to be added to the standard, and Firefox had unofficial support of it, but I can't find anything anywhere indicating if Chrome and Safari are supporting it (and IE will probably get it in 12 eyeroll).