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

RE: Server Push used for long polling

From: Mike Bishop <Michael.Bishop@microsoft.com>
Date: Thu, 15 Jan 2015 22:06:37 +0000
To: Greg Wilkins <gregw@intalio.com>
CC: Wenbo Zhu <wenboz@google.com>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <BL2PR03MB1325EDE5AF5108D77283C2F874E0@BL2PR03MB132.namprd03.prod.outlook.com>
You’re correct – that’s more equivalent.  But I’ve seen WebSockets used in the same way, even though it has broader capabilities.

From: Greg Wilkins [mailto:gregw@intalio.com]
Sent: Thursday, January 15, 2015 12:55 PM
To: Mike Bishop
Cc: Wenbo Zhu; HTTP Working Group
Subject: Re: Server Push used for long polling

On 15 January 2015 at 20:52, Mike Bishop <Michael.Bishop@microsoft.com<mailto:Michael.Bishop@microsoft.com>> wrote:

•         A long-lived response in which the server occasionally emits interesting new information (equivalent to WebSockets, if the client isn’t sending anything after the initial request)

This one is probably better likened to server-sent-events, which is effectively just a HTTP response content type.

Websocket should be likened to a long-lived client initiated stream without HTTP semantics that exchanges messages in both directions.
your other characterisations are spot on.

Greg Wilkins <gregw@intalio.com<mailto: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:07:05 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:36 UTC