Re: [w3ctag/design-reviews] Partition the HTTP cache (#424)

Hi,
This cache partitioning seems a good improvement, however I have a question about what is retrieved from the network.

Caches are not only to bring content faster to the client, but also to save bandwidth and resources server-side. CDNs and big content provider will be mostly unaffected by this, but it can have an effect on popular resources that are not in that case.

Could it be possible to do something else for resources that have explicit public caching instructions? (like `Cache-Control: public`) either an exemption, or storing in the cache the retrieval time and serve it back using that fake delay (exemption being the easiest to implement).

Also, could a retrieval should be done using a revalidation (to get timing information) but sending things back form the cache, to save at least the body or the HTTP response? 
Is internal cache storage duplicating the content or just the metadata?
Thanks,


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/424#issuecomment-542530717