This is a reply to an old message
(http://lists.w3.org/Archives/Public/public-webapps/2010AprJun/0087.html)
and I don't know if this goes to the right thread.
Would Server Sent Events be more or less efficient that Web Sockets?
Does one of these use less resources than the other? Or, are the
On Tue, 13 Apr 2010, Dominique Hazael-Massieux wrote:
Le lundi 12 avril 2010 à 17:47 +, Ian Hickson a écrit :
Server sent events doesn't require any change to the network, it's
compatible with almost any setup that uses HTTP today. Web Sockets
requires that intermediaries support
Le lundi 12 avril 2010 à 17:47 +, Ian Hickson a écrit :
Server sent events doesn't require any change to the network, it's
compatible with almost any setup that uses HTTP today. Web Sockets
requires that intermediaries support full-duplex connections. Server sent
events is compatible
Hi,
Given the overlap I perceive between Server Sent Events and the Web
Sockets spec, I would be interested to know what role Server Sent Events
fills that Web Sockets doesn't.
I understand that Server Sent Events allow for unidirectional
communication with the server, while Web sockets is
Hi,
Dominique Hazael-Massieux wrote on 12/04/2010 17:58:
Hi,
Given the overlap I perceive between Server Sent Events and the Web
Sockets spec, I would be interested to know what role Server Sent Events
fills that Web Sockets doesn't.
A remarkable (and IMHO probably most interesting)
On Mon, 12 Apr 2010, Dominique Hazael-Massieux wrote:
Given the overlap I perceive between Server Sent Events and the Web
Sockets spec, I would be interested to know what role Server Sent Events
fills that Web Sockets doesn't.
Server sent events doesn't require any change to the network,
