Everything is a cache. We are free to toss out local storage, databases, appcaches, cookies, etc. any time we want. I think the best way is to have a good eviction algorithm for local storage. What eviction algorithm are we using for the main browser cache? Perhaps some version of that that accounts for recency, usage, size, etc.?
Linus On Wed, Jul 29, 2009 at 11:31 AM, Ian Fette <[email protected]> wrote: > Add them to the malware blacklist :) > > 2009/7/29 Jeremy Orlow <[email protected]> > > On Wed, Jul 29, 2009 at 11:15 AM, Linus Upson <[email protected]> wrote: >> >>> I'm coming to the opinion that we should leverage the >>> install mechanism of the extension system for apps that need >>> special permissions, increased quotas, expanded lifetimes, etc. The >>> extension can be almost vacuous, and in our extension world exceptionally >>> lightweight. It only needs to make the special capability available to the >>> page. >>> As Maciej brought up on the whatwg list, the extension system gives us >>> multiple affirmative steps, >>> vetting, reputation and revocation. It also gives us a UI access point. All >>> of these are important for controlling apps that aren't safe and stateless. >>> >> >> I like this approach. >> >> So the only loose end is this: what should we do (if anything) about >> malicious apps using thousands of sub-domains (which are each their own >> origin, and thus get their own 5mb) to fill up your machine. As far as I >> know, no other browser deals with this and it hasn't ever been a problem >> (...yet), so I guess we can just ignore it for the time being? >> >> J >> > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
