Pepper: Split PpapiHostMsg_ChannelCreated use.

components/nacl/browser/nacl_process_host.h

Index: components/nacl/browser/nacl_process_host.h
diff --git a/components/nacl/browser/nacl_process_host.h b/components/nacl/browser/nacl_process_host.h
index 994799b8e982deec416571b79c2f2b3bccf51e81..89004081bb39b3d2186c02428ed4242f9080ffa6 100644
--- a/components/nacl/browser/nacl_process_host.h
+++ b/components/nacl/browser/nacl_process_host.h
@@ -176,8 +176,11 @@ class NaClProcessHost : public content::BrowserChildProcessHostDelegate {
                                    IPC::Message* reply_msg);
 #endif
 
-  // Called when a PPAPI IPC channel has been created.
+  // Called when the PPAPI IPC channel to the browser has been created.
   void OnPpapiChannelCreated(const IPC::ChannelHandle& channel_handle);
+  // Called when the PPAPI IPC channel to the renderer has been created.
+  void OnPpapiNaClChannelCreated(const IPC::ChannelHandle& channel_handle);

[bbudge, 2014/01/03 16:52:14]

In theory we may create more than one renderer channel. This is the normal PPAPI
setup, where there is only a single plugin process connected to multiple
renderers. That may never be supported for NaCl though.

How about calling these OnPpapiRendererChannelCreated and
OnPpapiBrowserChannelCreated?

+
   // Called by PluginListener, so messages from the untrusted side of
   // the IPC proxy can be handled.
   bool OnUntrustedMessageForwarded(const IPC::Message& msg);