Innovating with HTTP 2.0 Server Push: bit.ly/11a64YA - pushing resources, redirects, managing the client's cache, and more!

Innovating with HTTP 2.0 Server Push

HTTP 2.0 enables the server to send multiple responses for a single client request, which opens up an entire world of new optimization opportunities!

igvita.com
1
77
74
@igrigorik Cool stuff. What I don't get: Won't a server push needlessly push lots of things already cached on the client?
1
@stilkov right, that's where the efficiency part comes in: with inlining you have no choice, with push client can decline + server can learn
1
@igrigorik How can the server learn that the client didn't need a pushed resource? My understanding was the request will never reach it?
1
@stilkov the client must send a RST to cancel the stream. Alternatively, you can imagine other mechanisms to figure out cache state...
1
Replying to @igrigorik
@igrigorik With additional means – sure. But without them, the client can only cancel the complete stream, not individual resources. Right?

Jun 12, 2013 · 7:43 PM UTC

1
Replying to @stilkov
@stilkov each push resource is its own stream, hence can be canceled independently of parent stream.
1
@igrigorik Ah, OK. Sorry, not used to the terminology yet. Thanks! Very useful then.