Apache 2.4.17 with HTTP/2 support(icing.github.io) |
Apache 2.4.17 with HTTP/2 support(icing.github.io) |
What's sad is that this is yet another github page with #777 colored text on white background. The resulting contrast is too low to read comfortably!
First, push is very different than inlining, because individual resources are cacheable by the client, and inlined resources are not. There's a little handshake at the start of a push and if the client has (or doesn't otherwise want) the resource, it can cancel the push.
In my team's experiments with using push for HTML Imports, push ends up being better than inlining (using Polymer's vulcanize tool), even with a cold cache.
Also, push is relatively easy to implement if you use the response header approach, and was availably early on in mod_spdy.
Another method would be to add a headers to the response:
Server-Push: /relative/url
<Location />
ServerPush /static/css/main.css
ServerPush /static/js/main.js
</Location>
<LocationMatch "^/$">
ServerPush /static/img/gigantic-homepage-image.jpg
</LocationMatch>
<Location /maps/>
ServerPush /static/js/leaflet.js
</Location>
In a.b.c, odd b indicates the unstable or experimental branch, and even b's are used for major and backwards-compatibility breaking changes. Backwards-compatibility preserving changed can be introduced in c.
So 2.2 and 2.4 are pretty different versions, while 2.3 and 2.4 are closer except 2.3 is unstable. 2.4.0 is theoretically compatible with 2.4.17, except the latter has a lot more functionality and features.
(I'm assuming they are following "standard" semver rules here)
[1]: https://code.google.com/p/mod-spdy/wiki/OptimizingForSpdy#Us... [2]: https://github.com/GoogleChrome/http2push-gae
Jetty's approach to this problem is really interesting. Using HTTP referrer headers, it builds up a tree of resources that are often fetched together. Then, it optimistically pushes companion resources down. https://github.com/eclipse/jetty.project/blob/master/jetty-s...
The Jetty approach is clever, too, as would be things like scanning rel=prefetch links but simple declarative approaches have their moments, too. One thing the Jetty approach doesn't appear to offer is the ability to manage resources if not all resources are appropriate for every client so it would appear to do things like ship every size of a responsive image to every client.