I was wondering if worker processes have a profile affinity too. Eric's bringing up Databases in workers right now and databases are definitely per-profile. I'd vote to assert that a worker process only runs workers on behalf one profile, just like renderers.
>ResourceMessageFilter has a reference to a Profile object - are these Profile objects global > (for example, in the typical situation of a single profile + incognito, are there only two Profile > objects in the Browser process)? Yes. The fact that a worker process can host at most one worker certainly does simplify things for the time being ;) On Mon, Dec 7, 2009 at 11:37 AM, Drew Wilson <[email protected]> wrote: > Hi all, > > I'm trying to understand the current (and future) state of Profile support. > > Currently, SharedWorkers are shared by all windows in the system - any two > windows under the same domain can do "new SharedWorker(url)" and get a > reference to the same SharedWorker, and can use that worker to share data. > > I currently am special-casing incognito windows, so incognito windows don't > share workers with non-incognito workers, but I don't do anything to deal > with profiles in general (so if you were running with separate profiles, > those profiles would see one another's workers). > > I'm trying to figure out the best way to address this (and whether this is > something that needs to be addressed in the near term, given that we don't > officially support profiles - it sounds like chromeos may make some use of > them?). ResourceMessageFilter has a reference to a Profile object - are > these Profile objects global (for example, in the typical situation of a > single profile + incognito, are there only two Profile objects in the > Browser process)? > > -atw > > -- > Chromium Developers mailing list: [email protected] > View archives, change email options, or unsubscribe: > http://groups.google.com/group/chromium-dev -- Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
