Jeremy Morton wrote: > gavin wrote: >> On Oct 10, 3:09 pm, Jeremy Morton <[EMAIL PROTECTED]> wrote: >>> Could anyone explain to me why we have 2 redundant ways to, via prefs, >>> enable/disable network caching? network.http.use-cache seems to do the >>> same thing as browser.cache.disk.enable and browser.cache.memory.enable >>> combined. >> >> What leads you to that conclusion? From a quick look at LXR, >> "network.http.use-cache" is read by nsHttpHandler, while the other two >> prefs are read by the cache service. Without really looking into it >> further it would appear to me that they're not the same thing at all. >> Changing "network.http.use-cache" or changing both >> "browser.cache.disk.enable" and "browser.cache.memory.enable" may have >> the same observable effects if all you're looking at is caching >> behavior when visiting web sites using HTTP, but that doesn't mean >> they're redundant. >> >> Gavin >> > > Care to explain what they both do, then? I came to the conclusion from > reading the Mozillazine docs; look at: > http://kb.mozillazine.org/Network.http.use-cache > http://kb.mozillazine.org/Browser.cache.disk.enable > http://kb.mozillazine.org/Browser.cache.memory.enable > > And witness the very similar 'Background' text. I don't see a clear > difference documented there.
The world we can connect to and therefore cache is not just HTTP. Your two enable prefs control all caching, whatever the protocol. The http pref controls just http caching. Note the background text your point at from one of the articles: "This preference controls whether to use memory to cache decoded images, chrome (application user interface elements), and secure (https) pages" See how it alludes to there being more in the world than just http. _______________________________________________ dev-tech-network mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-network
