As we're having a technical discussion now anyway, any thoughts on
Server-Sent Events (SSE), a W3C Recommendation [1], compared to
WebSockets, a W3C Candidate Recommendation [2]? SSE is a match made in
heaven for open, one-way streaming APIs. Support in browsers is solid,
with the prominent exception being MSIE (not sure about Spartan):
http://caniuse.com/#search=server-sent%20events. Fair enough,
WebSockets wins implementation-wise:
http://caniuse.com/#search=websockets. Also check a comparison of
WebSockets vs. SSE:
http://www.html5rocks.com/en/tutorials/eventsource/basics/#toc-introduction….
What do you think?
Cheers,
Tom
--
[1]
http://www.w3.org/TR/eventsource/
[2]
http://www.w3.org/TR/websockets/
--
Dr. Thomas Steiner, Employee, Google Inc.
http://blog.tomayac.com,
http://twitter.com/tomayac
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iFy0uwAntT0bE3xtRa5AfeCheCkthAtTh3reSabiGbl0ck0fjumBl3DCharaCTersAttH3b0ttom.hTtP5://xKcd.c0m/1181/
-----END PGP SIGNATURE-----