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

Re: Recursive HTTP/2 Push

From: Simone Bordet <simone.bordet@gmail.com>
Date: Tue, 9 Feb 2016 11:14:46 +0100
Message-ID: <CAFWmRJ1S1u4GOtZxVW+qLGe+ypSi_w=XB9LKj1mLKbUtebn7ag@mail.gmail.com>
To: HTTP Working Group <ietf-http-wg@w3.org>
Hi,

thanks for the feedback so far !

On Mon, Feb 8, 2016 at 8:37 PM, Patrick McManus <pmcmanus@mozilla.com> wrote:
> I guess I would say that the spec is pretty clear when it says peer
> initiated - it means to forbid this. OTOH I think you make a good argument
> about the resource tree.

If servers can only push on peer-initiated streams, there are two cases:

A) the client requests for recursive.html, gets recursive.css pushed,
but it always have to explicitly request recursive.png.

B) the server flattens the resource tree, so that the client requests
recursive.html, and gets recursive.css and recursive.png pushed.

I think we'll go for B) in Jetty, unless there are objections stating
that this is not intended behavior.

Thanks !

-- 
Simone Bordet
http://bordet.blogspot.com
---
Finally, no matter how good the architecture and design are,
to deliver bug-free software with optimal performance and reliability,
the implementation technique must be flawless.   Victoria Livschitz
Received on Tuesday, 9 February 2016 10:15:15 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 22 March 2016 12:47:11 UTC