On Tue, Mar 24, 2009 at 10:00 AM, Amanda Walker <[email protected]> wrote:
> 2009/3/24 John Abd-El-Malek <[email protected]>: > > Right, this is used so that if the user starts Chrome a second time, it > > tells the currently running exe to open a new tab. This is the standard > way > > of doing it on Windows, but I don't know how Mac/Linux apps enforce > > single-instance semantics. We should first figure out if this code is > > needed before porting it.. > > Mac OS X handles this via the UI--if you try to launch an > already-running application through the Finder, Dock, etc., the > already running instance is brought to the front. While nothing in > the underlying OS enforces single-instance semantics, the only way to > get multiple instances within a single user session is to open a > command line and explicitly launch them (or do the equivalent from > another program or script). Additional instances can of course be > launched in other user sessions simply by switching to another session > and launching the application normally. > > It's not at all clear to me that we need to explicitly filter out > multiple instances on the Mac; if we do, we will need to scope such > filtering to a single user session, which will require using > Mac-specific APIs. I would suggest that we postpone this until and > unless we find a demonstrated need for it. A lot of the code that touches databases/files in the user-data-dir assume they're the only ones accessing them. If multiple instances use the data, there could be corruption. > > > --Amanda > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
