On Sat, Mar 28, 2009 at 5:35 PM, Dan Kegel <[email protected]> wrote:
> > On Sat, Mar 28, 2009 at 4:59 PM, Erik Kay <[email protected]> wrote: > > ...When you update > > in place, resources can be changed, removed, etc. So let's say that > > some dll hasn't been loaded yet, but then an autoupdate happens. Now > > you trigger loading the dll, and you crash, because this kind of > > forwards compatibility is never tested (nor should it be). This can > > happen with simple data files as well (although we don't have many of > > those at the moment). This is why all of the loaded code and > > resources are in a versioned directory (minus dictionaries, but that's > > a separate issue). > > > > How will in-place updating work on the Mac and Linux? > > For Linux, I was imagining that we'd open handles at > startup to any file we'd need, and then never open > any more handles after that. That way, the window > during which an update could screw you would be > brief (i.e. only if you started the app halfway through > installation of an update could it misbehave). We looked into this more at one point and noticed that mmap doesn't make any promises when the file on disk changes. We'll probably have to use versioned directories as well to avoid problems when updating while running. --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
