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

Re: Last Call: <draft-ietf-httpbis-http2-16.txt> (Hypertext Transfer Protocol version 2) to Proposed Standard

From: Patrick McManus <pmcmanus@mozilla.com>
Date: Tue, 6 Jan 2015 10:22:18 -0500
Message-ID: <CAOdDvNp2i5NUFP8PKn13NYOFg481EJcitd67_k5r0N_ziwJWag@mail.gmail.com>
To: Stefan Eissing <stefan.eissing@greenbytes.de>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
On Tue, Jan 6, 2015 at 8:13 AM, Stefan Eissing <stefan.eissing@greenbytes.de
> wrote:

> 3. Clarification on server-initiated push?
> In discussions with colleagues some had the notion that HTTP2 would allow
> server initiated "requests". My reading of the draft is that this is not
> really the case. Server pushes are only defined for streams opened by the
> client.
> - Is this the correct reading of the spec?
>

That's right. The server can push 0..N transactions on any stream opened by
the client.


> - If yes, has HTTP2 any advise how to best do long polling or what is the
> recommended alternative?
>

client opens a stream indicating its interested in an event stream.. the
server may/may not provide a response but it leaves that stream open for
the duration of time it might push. When it pushes events (represented by a
request/response pair) it associates the new even streams with the client
stream. There can be N of these events in parallel, which makes it
considerably nicer than long polling. Whenever the server decides it is
done pushing things it can close the odd stream.. or the client can stream
reset the odd stream if it decides its done first.
Received on Tuesday, 6 January 2015 15:22:41 UTC

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