W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2015

Re: Server Push used for long polling

From: Greg Wilkins <gregw@intalio.com>
Date: Thu, 15 Jan 2015 23:22:53 +0100
Message-ID: <CAH_y2NG6C-gF5jjpKgO+TOv-4KKpxDL6tSumkGgmOEwFG3zcrQ@mail.gmail.com>
To: Mike Bishop <Michael.Bishop@microsoft.com>
Cc: Wenbo Zhu <wenboz@google.com>, HTTP Working Group <ietf-http-wg@w3.org>
On 15 January 2015 at 23:06, Mike Bishop <Michael.Bishop@microsoft.com>

> You’re correct – that’s more equivalent.  But I’ve seen WebSockets used in
> the same way, even though it has broader capabilities.


The problem with server sent events is that there is no guarantee that an
intermediary will forward the content in chunks.   A caching proxy might
try to cache the entire response.

So websocket is preferable if it is able to connect.    Never really
understood why W3C went for two such similar mechanisms in HTML5 when
websockets can do the job of both.


Greg Wilkins <gregw@intalio.com>  @  Webtide - *an Intalio subsidiary*
http://eclipse.org/jetty HTTP, SPDY, Websocket server and client that scales
http://www.webtide.com  advice and support for jetty and cometd.
Received on Thursday, 15 January 2015 22:23:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:42 UTC