You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cache Digests could be practical for Web bundles: using them, it could be possible to "Server Push" the web bundle, and the server could include in the pushed bundle only what isn't already in the cache of the browser. So we (theoretically) could have the best of both approaches; a good compression, one less RTT and a good hit rate.
Is it something we should investigate? (I initially discussed this privately with @KenjiBaheux in discussions related to the removal of Server Push from Chrome.)
The text was updated successfully, but these errors were encountered:
@yoavweiss and @littledan are working on a way to serve just the parts of the bundle that aren't in cache. I'll let them point at their latest design sketches.
Cache Digests could be practical for Web bundles: using them, it could be possible to "Server Push" the web bundle, and the server could include in the pushed bundle only what isn't already in the cache of the browser. So we (theoretically) could have the best of both approaches; a good compression, one less RTT and a good hit rate.
Is it something we should investigate? (I initially discussed this privately with @KenjiBaheux in discussions related to the removal of Server Push from Chrome.)
The text was updated successfully, but these errors were encountered: