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.
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 -~----------~----~----~----~------~----~------~--~---
