On Tue, Dec 16, 2008 at 5:47 PM, [email protected] < [email protected]> wrote:
> > We need to at least support per-profile enabling/disabling of > extensions. The extension package may live outside the profile > directory, but if another profile has Random Extension X enabled, I > shouldn't be forced to use it as well. Enabling / disabling of extensions per profile seems like the right thing to do, but at least to me, installation outside the profile directory would be more natural. We already have an install path that is per user so most of the time the person using a profile X is the same one that installed the browser and any additional extensions, and it would be natural to have them available on all profiles. > > As for the technical details of request interception, every request > has an URLRequestContext, which has a 1-1 mapping to a Profile object. > Perhaps you can use that to either store the info you need or get > access to the right Profile. The thing you need to be careful about > is that Profiles can only be accessed on the UI thread. I had to deal > with a similar problem when working out request interception for > Gears, so maybe I can help you with details. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
