3 ms·
It didn't catch on because it was hard to see the benefits, and if done incorrectly, could actually make things slightly slower. Essentially, the server had to
by KingMob 2y ago
It didn't catch on because it was hard to see the benefits, and if done incorrectly, could actually make things slightly slower.
Essentially, the server had to do things like compute RTT and understand the status of the browser's cache to do optimal push.
- a-dub 2y agohmm, maybe the client could include a same origin cache state bloom filter in the request. although i suppose it's a solved problem these days.
- KingMob 2y agoBloom filters are small relative to the amount of data they can hash, but aren't realistic bloom filters still tens of kB at minimum? Might be too heavyweight to send up.