Re: Using HTTP cache control for invalidating a cache of parsed objects
Brian Smith <[email protected]>
| Newsgroups | gmane.comp.mozilla.devel.netlib |
|---|---|
| Message-ID | <1307782112.89535.1320698238897.JavaMail.root@zimbra1.shared.sjc1.mozilla.com> |
Henri Sivonen wrote: > Should a higher-level cache even want to maintain HTTP-correct cache > coherence in situations where determining cache coherence would > require pinging the origin server with an etag and should a > higher-level cache work with expiry times instead and simply not > support etags? > > (I'm thinking of a localization resource cache for a situation where > L20n grows past chrome: URLs to work with HTTP-originating > localization resources that are shared between documents within an > origin.) I don't understand your example very well. Why wouldn't the normal HTTP cache work as is? What is happening in the higher-level cache? Thanks, Brian