Embracre HTTP2 Server Push
summary
HTTP/2 server push can cut round‑trip latency by proactively sending dependent assets and uses a push promise → RST_STREAM handshake so the browser can cancel duplicates; major browsers support H2 (~75% global, ~90% US) while nginx lacked push then and CDNs like Akamai and Cloudflare offer push APIs. InterlockJS generates per‑module output files plus a server push manifest so builds map modules to filenames; the project is alpha but shows reduced latency and workable caching.
AI-written summary · about
chapters (12)
- 0:00Introduction to HTTP/2
- 3:58HTTP/2 evolution story
- 10:41HTTP/1.1 limitations
- 11:23Latency vs bandwidth impact
- 13:08H1 vs H2 waterfall comparison
- 14:13Server push benefits
- 15:20Server push mechanics
- 15:43Browser and server support
- 16:24Bundling in H2 era
- 17:49Introducing Interlock JS
- 20:59H2 optimized output
- 23:04Push manifest and conclusion
related talks
40mTo push, or not to push?! - The future of HTTP/2 server push
26mTo push, or not to push?! - The future of HTTP/2 server push
03h 16mPUSHing web app performance with HTTP/2
15mBundling With H2 Server Push
19mHTTP/2 is here, now let's make it easy
01h 03mWhirlwind tour through the HTTP2 spec
50mHigh-performance web apps using HTTP/2
01h 00mHTTP/2 - The future of the web today
