summaryrefslogtreecommitdiffstats
path: root/extensions/common/extension_messages.h
diff options
context:
space:
mode:
authorkalman <kalman@chromium.org>2015-08-21 12:30:13 -0700
committerCommit bot <commit-bot@chromium.org>2015-08-21 19:31:00 +0000
commit12033f1290753504a3c324293689313b890e4ef2 (patch)
tree84493e36fd5ef8f215bcde3cd82aa638dac52d06 /extensions/common/extension_messages.h
parentb3ad146d98e8e67187e4f072676afbe210e73042 (diff)
downloadchromium_src-12033f1290753504a3c324293689313b890e4ef2.zip
chromium_src-12033f1290753504a3c324293689313b890e4ef2.tar.gz
chromium_src-12033f1290753504a3c324293689313b890e4ef2.tar.bz2
Implement the wake-event-page internal extension API.
This is implemented purely using IPC because it will be used from worker contexts, which don't have access to extension bindings. The next step will be to add worker thread support so the renderer side is structured to easily accommodate for that, once the public content API is chaned to allow it. It will be used in the public chrome.runtime.getBackgroundClient() exposed to service workers. BUG=501569 R=rdevlin.cronin@chromium.org, palmer@chromium.org Review URL: https://codereview.chromium.org/1294993004 Cr-Commit-Position: refs/heads/master@{#344834}
Diffstat (limited to 'extensions/common/extension_messages.h')
-rw-r--r--extensions/common/extension_messages.h11
1 files changed, 11 insertions, 0 deletions
diff --git a/extensions/common/extension_messages.h b/extensions/common/extension_messages.h
index 49aee48..d799781 100644
--- a/extensions/common/extension_messages.h
+++ b/extensions/common/extension_messages.h
@@ -506,6 +506,11 @@ IPC_MESSAGE_ROUTED1(ExtensionMsg_NotifyRenderViewType,
IPC_MESSAGE_CONTROL1(ExtensionMsg_UsingWebRequestAPI,
bool /* webrequest_used */)
+// The browser's response to the ExtensionMsg_WakeEventPage IPC.
+IPC_MESSAGE_CONTROL2(ExtensionMsg_WakeEventPageResponse,
+ int /* request_id */,
+ bool /* success */)
+
// Ask the lazy background page if it is ready to be suspended. This is sent
// when the page is considered idle. The renderer will reply with the same
// sequence_id so that we can tell which message it is responding to.
@@ -769,6 +774,12 @@ IPC_MESSAGE_ROUTED1(ExtensionHostMsg_OnWatchedPageChange,
IPC_MESSAGE_CONTROL1(ExtensionHostMsg_TransferBlobsAck,
std::vector<std::string> /* blob_uuids */)
+// Asks the browser to wake the event page of an extension.
+// The browser will reply with ExtensionHostMsg_WakeEventPageResponse.
+IPC_MESSAGE_CONTROL2(ExtensionHostMsg_WakeEventPage,
+ int /* request_id */,
+ std::string /* extension_id */)
+
// Tells listeners that a detailed message was reported to the console by
// WebKit.
IPC_MESSAGE_ROUTED4(ExtensionHostMsg_DetailedConsoleMessageAdded,