diff options
| author | aa@chromium.org <aa@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-04-26 23:51:09 +0000 |
|---|---|---|
| committer | aa@chromium.org <aa@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-04-26 23:51:09 +0000 |
| commit | 39755c360cd4c5884f590aa0548cdd72d30dbdb0 (patch) | |
| tree | bf599e2be3b4b226f7be5ca4a3327d22e4561f2b /chrome/common/extensions/extension_messages.h | |
| parent | 84ec056834c1625b7b7d316817b018564f76e22a (diff) | |
| download | chromium_src-39755c360cd4c5884f590aa0548cdd72d30dbdb0.zip chromium_src-39755c360cd4c5884f590aa0548cdd72d30dbdb0.tar.gz chromium_src-39755c360cd4c5884f590aa0548cdd72d30dbdb0.tar.bz2 | |
Revert 83100 - Remove weird dependency on extensions from webui.Re-plumb extension request messages in a more sane way.Before, each RVH had ProcessWebUIMessage(), which wasserving as a manual way of plumbing both WebUI andextension messages to the right place, even though onlya few RVHD responded to either message.Instead of this, we now just teach more of the stack howto handle IPC messages in general, and delegate them upthrough the stack, giving each layer a chance to handlethem if it knows how.The result is simpler and smaller:179 insertions(+), 252 deletions(-)BUG=80311Review URL: http://codereview.chromium.org/6901021
TBR=aa@chromium.org
Review URL: http://codereview.chromium.org/6905045
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@83103 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/common/extensions/extension_messages.h')
| -rw-r--r-- | chrome/common/extensions/extension_messages.h | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/chrome/common/extensions/extension_messages.h b/chrome/common/extensions/extension_messages.h index 74378dd..f2f5c34 100644 --- a/chrome/common/extensions/extension_messages.h +++ b/chrome/common/extensions/extension_messages.h @@ -16,7 +16,7 @@ #define IPC_MESSAGE_START ExtensionMsgStart // Parameters structure for ExtensionHostMsg_Request. -IPC_STRUCT_BEGIN(ExtensionHostMsg_Request_Params) +IPC_STRUCT_BEGIN(ExtensionHostMsg_DomMessage_Params) // Message name. IPC_STRUCT_MEMBER(std::string, name) @@ -214,7 +214,7 @@ IPC_MESSAGE_ROUTED1(ExtensionMsg_GetApplicationInfo, // A renderer sends this message when an extension process starts an API // request. The browser will always respond with a ExtensionMsg_Response. IPC_MESSAGE_ROUTED1(ExtensionHostMsg_Request, - ExtensionHostMsg_Request_Params) + ExtensionHostMsg_DomMessage_Params) // Notify the browser that the given extension added a listener to an event. IPC_MESSAGE_CONTROL2(ExtensionHostMsg_AddListener, |