Re: Experiences with HTTP/2 server push

I didn't read through this in detail, but there is a fairly big error
here when it comes to the description of using priorities.  You say:

> One way to implement this is for the server to update its HTTP/2 priority tree, **then send PRIORITY frames to the client that make A the exclusive parent of C** and C the exclusive parent of D. This is an attractive implementation because the server can continue using the HTTP/2 priority tree to order requests C, D, and B.

The server can't send PRIORITY frames in this way.  Or at least, that
won't have the effect you think it does.

The server can (and should) just send as it sees fit, using as input
its own knowledge and the priority that the client has provided.  If
the server sends PRIORITY, that is to affect client processing (hint:
that's not going to happen here). Given that the space that you are
examining is a problem for server-to-client transmission only, the
server expressing priority is pointless.

On 4 August 2016 at 10:21, Tom Bergan <> wrote:
> Hi all,
> Our team has been experimenting with H2 server push at Google for a few
> months. We found that it takes a surprising amount of careful reasoning to
> understand why your web page is or isn't seeing better performance with H2
> push. We also encountered a lack of good documentation: How should one go
> about using H2 push? What are the best practices? We tried to distill our
> experiences into five "rules of thumb" that are described in this doc:
> The doc is a little long, but the first two pages give a decent tl;dr. I
> suspect the ideas and conclusions will be "obvious" to many people on this
> mailing list, at least in hindsight. Hopefully other folks interested in H2
> server push will find this useful. Let us know if you have any comments.
> -Tom, Simon, and Michael

Received on Friday, 5 August 2016 12:28:56 UTC