Browser side implementation of browser plugin

content/common/browser_plugin/browser_plugin_messages.h

Index: content/common/browser_plugin/browser_plugin_messages.h
diff --git a/content/common/browser_plugin/browser_plugin_messages.h b/content/common/browser_plugin/browser_plugin_messages.h
new file mode 100644
index 0000000000000000000000000000000000000000..9db3c9c36472532cd55031c38d81ab96ac6b684b
--- /dev/null
+++ b/content/common/browser_plugin/browser_plugin_messages.h
@@ -0,0 +1,75 @@
+// Copyright (c) 2012 The Chromium Authors. All rights reserved.

[jam, 2012/04/05 21:03:08]

please just keep this in content/common without a browser_plugin subdirectory,
since it's not terribly useful to have it for only one file

+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+// Multiply-included message header, no traditional include guard.
+
+#include <string>
+
+#include "base/basictypes.h"
+#include "base/process.h"
+#include "content/common/content_export.h"
+#include "content/public/common/common_param_traits.h"
+#include "ipc/ipc_channel_handle.h"
+#include "ipc/ipc_message_macros.h"
+#include "ipc/ipc_message_utils.h"
+#include "ui/gfx/size.h"
+
+#undef IPC_MESSAGE_EXPORT
+#define IPC_MESSAGE_EXPORT CONTENT_EXPORT

[jam, 2012/04/05 21:03:08]

nit: i believe you only need these two lines if you're using these ipcs from
tests. since you're not, then you don't need them. see drag_messages.h for ex

+
+#define IPC_MESSAGE_START BrowserPluginMsgStart
+
+// Browser plugin messages
+
+// -----------------------------------------------------------------------------
+// These messages are from the host renderer to the browser process
+
+// A renderer sends this to the browser process when it wants to
+// create a browser plugin.  The browser will create a guest renderer process
+// if necessary.
+IPC_MESSAGE_ROUTED4(BrowserPluginHostMsg_OpenChannel,
+                    int /* plugin instance id*/,
+                    long long /* frame id */,
+                    std::string /* src */,
+                    gfx::Size /* size */)
+
+// -----------------------------------------------------------------------------
+// These messages are from the browser process to the guest renderer.
+
+// Creates a channel to talk to a renderer. The guest renderer will respond
+// with BrowserPluginHostMsg_ChannelCreated.
+IPC_MESSAGE_CONTROL2(BrowserPluginMsg_CreateChannel,
+                     base::ProcessHandle /* host_renderer_process_handle */,
+                     int /* host_renderer_id */)
+
+// -----------------------------------------------------------------------------
+// These messages are from the guest renderer to the browser process
+
+// Reply to BrowserPluginMsg_CreateChannel. The handle will be NULL if the
+// channel could not be established. This could be because the IPC could not be
+// created for some weird reason, but more likely that the renderer failed to
+// initialize properly.
+IPC_MESSAGE_CONTROL1(BrowserPluginHostMsg_ChannelCreated,
+                     IPC::ChannelHandle /* handle */)
+
+// Indicates the guest renderer is ready in response to a ViewMsg_New
+IPC_MESSAGE_ROUTED0(BrowserPluginHostMsg_GuestReady)
+
+// A host renderer sends this message to the browser when it wants
+// to resize a guest plugin container so that the guest is relaid out
+// according to the new size.
+IPC_MESSAGE_ROUTED2(BrowserPluginHostMsg_ResizeGuest,
+                    int32, /* width */
+                    int32  /* height */);
+
+// -----------------------------------------------------------------------------
+// These messages are from the browser process to the host renderer.
+
+// A guest instance is ready to be placed.
+IPC_MESSAGE_ROUTED3(BrowserPluginMsg_GuestReady_ACK,
+                    int /* instance id */,
+                    base::ProcessHandle /* plugin_process_handle */,
+                    IPC::ChannelHandle /* handle to channel */)
+
+