3 ms·
(although server-sent-events are supported by just about everything except IE: http://caniuse.com/eventsource http://caniuse.com/eventsource )
by mcav 12y ago
(although server-sent-events are supported by just about everything except IE: http://caniuse.com/eventsource http://caniuse.com/eventsource )
- panzi 12y agoGiven that IE 10+ supports web sockets I don't really see the need for server sent events. What can you do with server sent events that you cannot do with web sockets? I guess one could deprecate SSE in favor of WS.
- chc 12y agoIt's not what you can do, but what you have to do. Websockets are to Server-Sent Events as jet planes are to wheelbarrows. Yes, the stuff jet planes can carry is a superset of the stuff wheelbarrows can carry, but the cost is greater and it ends up being a suboptimal in many cases where you'd want to use a wheelbarrow.
- derefr 12y agoAlso, most people who think they want the semantics of websockets, really want the semantics of SSE. I've seen many, many webapps that basically build SSE on top of websockets.
- stephenr 12y agoSSE is trivial to support via a polyfill, and has none of the connectivity issues websockets has, so it's capable across a much wider array of devices/software both client side and server/network side I feel that websockets is like the xml of this decade - "everyone is using it" so everyone wants to use it.