HTTP/2 is not the future, it’s the present

Re:HTTP/2 is not the future, it’s the present by spankalee on Wednesday April 12, 2017 @12:47PM (#14099413)

For those interested in HTTP/2 Push, check out Eric Bidelman's Push Manifest format[1], which is a JSON format describing the dependencies to push for any request URL. You can generate the manifest by hand or with tools, and then there are servers that can read the manifest and push the right resources.[2]

In Polymer we're most of the way done with support for automatically generating push manifests from a dependency analysis of your project[3] and have push manifest support in our dev server and soon a small production server, so you can `polymer deploy` and get a push-enabled site.

[1]: https://github.com/GoogleChrome/http2-push-manifest

[2]: https://github.com/GoogleChrome/http2push-gae

[3]: https://github.com/Polymer/polymer-build/pull/172

[ Parent | on HN ]

Re:HTTP/2 is not the future, it’s the present by pcollins123 on Thursday April 13, 2017 @10:10AM (#14107025)

This is really interesting thanks.

Doesn't this lead to the most highly used static assets being pushed for every subsequent request? Isn't that wasteful?

I use varnish cache extensively and am considering writing a probabilistic server push module. It could keep track of subsequent requests and push the next set of assets. This is more of a server module approach rather than client side.

Any thoughts on that?

[ Parent | on HN ]