3 ms·
What really killed it was an awful implementation. It did not simply push things into browser’s cache. Instead, pushed items were held in some kind of temporary
by pornel 4y ago
What really killed it was an awful implementation. It did not simply push things into browser’s cache. Instead, pushed items were held in some kind of temporary purgatory, and would be discarded if browser didn’t immediately have a need to request the pushed resource.
- jgraettinger1 4y agoIIRC there were two reasons for this. One was an information-leak concern whose details I don't fully remember. The other is flow control. A server push doesn't automatically send the entire object. It opens a new stream and fills the window, but the client must actively read / ack the stream for the remainder to be sent. To do otherwise would allow the server to de-facto violate the client's stated flow control settings and potentially DoS their network link.