Introducing ExtensionProcessManager. This manages the ExtensionViews to

ensure there is only 1 process per extension.

I also changed ExtensionMessageService from singleton to one instance per
Profile.  This means messages can only be passed to extensions and scripts
within the same profile.
Review URL: http://codereview.chromium.org/62132

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

1 files changed, 5 insertions, 7 deletions

diff --git a/chrome/browser/views/hwnd_html_view.h b/chrome/browser/views/hwnd_html_view.h
index b4a0d6a..9a55496 100644
--- a/chrome/browser/views/hwnd_html_view.h
+++ b/chrome/browser/views/hwnd_html_view.h
@@ -10,6 +10,7 @@
 
 class RenderViewHost;
 class RenderViewHostDelegate;
+class SiteInstance;
 
 // A simple view that wraps a RenderViewHost in an HWNDView to facilitate
 // rendering HTML as arbitrary browser views.
@@ -17,13 +18,7 @@ class RenderViewHostDelegate;
 class HWNDHtmlView : public views::HWNDView {
  public:
   HWNDHtmlView(const GURL& content_url, RenderViewHostDelegate* delegate,
-               bool allow_dom_ui_bindings)
-      : render_view_host_(NULL),
-        content_url_(content_url),
-        allow_dom_ui_bindings_(allow_dom_ui_bindings),
-        delegate_(delegate),
-        initialized_(false) {
-  }
+               bool allow_dom_ui_bindings, SiteInstance* instance);
   virtual ~HWNDHtmlView();
 
   RenderViewHost* render_view_host() { return render_view_host_; }
@@ -50,6 +45,9 @@ class HWNDHtmlView : public views::HWNDView {
   // Our HTML rendering component.
   RenderViewHost* render_view_host_;
 
+  // The site instance that the renderer belongs to.
+  SiteInstance* site_instance_;
+
   // Whether or not the rendered content is permitted to send messages back to
   // the view, through |delegate_| via ProcessDOMUIMessage.
   bool allow_dom_ui_bindings_;