Refactoring of new IPC-only pepper implementation

content/browser/ppapi_plugin_process_host.cc

Index: content/browser/ppapi_plugin_process_host.cc
diff --git a/content/browser/ppapi_plugin_process_host.cc b/content/browser/ppapi_plugin_process_host.cc
index 518b4285d7b32e9d7947cecd94d31118bf1170ae..6ca42358c13f5e0a699be8c8bf478221efaf51b7 100644
--- a/content/browser/ppapi_plugin_process_host.cc
+++ b/content/browser/ppapi_plugin_process_host.cc
@@ -123,9 +123,11 @@ PpapiPluginProcessHost::PpapiPluginProcessHost(
   process_.reset(new BrowserChildProcessHostImpl(
       content::PROCESS_TYPE_PPAPI_PLUGIN, this));
 
-  filter_ = new PepperMessageFilter(
-      PepperMessageFilter::PLUGIN, host_resolver,
-      ppapi::PpapiPermissions(info.permissions));
+  filter_ = new PepperMessageFilter(PepperMessageFilter::PLUGIN,
+                                    host_resolver);
+
+  ppapi::PpapiPermissions permissions(info.permissions);
+  host_impl_.reset(new content::BrowserPpapiHostImpl(this, permissions));

[raymes, 2012/07/25 16:53:22]

How do messages get routed to the BrowserPppapiHostImpl?

[brettw, 2012/07/30 05:46:37]

They don't yet. The browser side still has some stuff to do.

 
   file_filter_ = new PepperTrustedFileMessageFilter(
       process_->GetData().id, info.name, profile_data_directory);