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 20:30:33 +0100
Message-ID: <CAH_y2NFKiD627NQ79o0yV3+83QBFn3yMr7a=QKfuy_Tt5eNLCg@mail.gmail.com>
To: Wenbo Zhu <wenboz@google.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
On 15 January 2015 at 20:23, Wenbo Zhu <wenboz@google.com> wrote:

> Wouldn't you need an open (i.e. pre-opened) websocket stream to do this?
> IMO, spontaneous server-push (i.e. without a client-initiated stream) is a
> unique feature of PP, which is orthogonal to the problem of streaming data
> from the server to client.


I'm not saying that PP is not needed.   It looks well designed for purpose
and that is pushing associated resources to a HTTP request. PP is one of
the key features in HTTP2 that make it worthwhile deploying now despite all
it's warts.

What I don't think it is good for is replacing long polling as a way of
providing a server to client messaging transport.  That is what websockets
has been designed for and we should look to how websockets can be well
carried over HTTP2 rather than how we can trick HTTP Push into being a
messaging transport for non HTTP messages.


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 19:31:04 UTC

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