Remove ExtensionProcessManager and move its functionality onto

ExtensionsService.

Also add "chrome-extension" to the list of schemes that BrowsingInstance
groups per-site, instead of per-tab.  This means that navigating to an
extension URL will use the same process as a running extension toolstrip.
Review URL: http://codereview.chromium.org/77002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@13887 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 4 insertions, 1 deletions

diff --git a/chrome/browser/extensions/extension_message_service.h b/chrome/browser/extensions/extension_message_service.h
index f938b51..d4eb856 100755
--- a/chrome/browser/extensions/extension_message_service.h
+++ b/chrome/browser/extensions/extension_message_service.h
@@ -13,6 +13,7 @@
 #include "chrome/common/notification_observer.h"
 
 class ExtensionView;
+class ListValue;
 class ResourceMessageFilter;
 class URLRequestContext;
 
@@ -61,7 +62,9 @@ class ExtensionMessageService : public NotificationObserver {
                const NotificationSource& source,
                const NotificationDetails& details);
 
-  std::set<int> GetUniqueProcessIds();
+  // Send an event to every registered extension renderer.
+  void DispatchEventToRenderers(
+      const std::string& event_name, const std::string& event_args);
 
  private:
   // A map of extension ID to the render_process_id that the extension lives in.