On Mon, Jul 13, 2009 at 4:12 PM, Aaron Boodman <[email protected]> wrote:
> On Mon, Jul 13, 2009 at 4:08 PM, Erik Kay<[email protected]> wrote: > > We'd probably need to store the list of sanitized images in prefs to > avoid > > the extra stat for every image, but OK. > > There's on extra stat, read, and write the first time an image is > used. This does not seem like a big deal to me (not worth piling more > state into preferences for). These images are not used to draw the > main UI, and startup doesn't block on them. If we ever add the magical > file cache thing that would be used generally for extension resources, > it would presumably help with this too. But it doesn't feel like > something that needs optimizing by itself. > > > The other loss here is that we could have caught those problems at > package > > time. Without the declarative list, we can't do that either. > > True. You know I'm big on error handling, but I feel like ease-of-use wins > here. > As I said originally, I think the proposal sounds reasonable. It'a always worth going through the downsides. Erik --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
