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

Re: Recursive HTTP/2 Push

From: Daniel Stenberg <daniel@haxx.se>
Date: Tue, 9 Feb 2016 11:29:43 +0100 (CET)
To: Simone Bordet <simone.bordet@gmail.com>
cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <alpine.DEB.2.20.1602091119370.6404@tvnag.unkk.fr>
On Tue, 9 Feb 2016, Simone Bordet wrote:

> 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.

Push doesn't imply anything about the resources having to be in a resource 
tree or anything like that. It is just objects the server can offer to the 
client before the client asks for it themselves.

If clients are likely to want both these files after having asked for 
"recursive.html", then I'd say (B) makes the most sense and (A) seems a bit 
limited. But ultimately, that's up to the server to decide.


  / daniel.haxx.se
Received on Tuesday, 9 February 2016 10:30:18 UTC

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