Bundling With H2 Server Push
summary
Demos show two working tools: http2 server pushes individual assets over HTTP/2, uses zopfli-style compression (higher CPU then cached), auto-generates local HTTPS certs, and implements cache-digest via a Bloom filter with a service-worker cookie fallback so pushes skip already-cached files — observed page load drops from ~3s to ~1s (≈3× faster) in the demo. The other tool unbundle traces deps with Browserify Babel and SystemJS, runs parallel incremental builds in milliseconds, serves files individually, and uses xx64 emoji fingerprints plus Cache-Control immutable to avoid unnecessary updates.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:20Pros
- 3:04HTTP to Server
- 5:55Bandwidth Delay
- 8:10Bloom Filters
- 9:04Unbundle
- 12:08Browser 54
- 12:48Watch Mode
- 13:07Service Workers
- 13:19Cache API
- 13:50CacheControlImmutable
- 14:25Emoji
- 14:38Hex
- 14:59Outro
related talks
03h 16mPUSHing web app performance with HTTP/2
25mHTTP/2 is coming! Unbundle all the things?!?
24mEmbracre HTTP2 Server Push
50mHigh-performance web apps using HTTP/2
40mTo push, or not to push?! - The future of HTTP/2 server push
24mHTTP/2, One Frame At A Time
26mTo push, or not to push?! - The future of HTTP/2 server push
39mHTTP2, one frame at a time