Add skeleton implementation of ExtensionPushMessagingEventRouter.

chrome/common/extensions/api/experimental_push_messaging.idl

Index: chrome/common/extensions/api/experimental_push_messaging.idl
diff --git a/chrome/common/extensions/api/experimental_push_messaging.idl b/chrome/common/extensions/api/experimental_push_messaging.idl
new file mode 100644
index 0000000000000000000000000000000000000000..ce0da6ab6b9efe7c023a3b3df839a94cb9618070
--- /dev/null
+++ b/chrome/common/extensions/api/experimental_push_messaging.idl
@@ -0,0 +1,21 @@
+// Copyright (c) 2012 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+// File-level comment to appease parser. Eventually this will not be necessary.
+
+namespace experimental.pushMessaging{

[Mihai Parparita -not on Chrome, 2012/08/01 20:05:50]

Add a [nodoc] annotation for now, so that people don't try to use it while it's
still stubbed out (and so that you don't have to regenerate docs when fleshing
it out).

[dcheng, 2012/08/01 21:15:33]

Done.

+  dictionary Message {
+    // The subchannel the message was sent on.
+    long subchannel;

[Mihai Parparita -not on Chrome, 2012/08/01 20:05:50]

ID fields in API structures generally have an Id suffix (cf. processId, tabId,
socketId, vendorId, etc.)

[dcheng, 2012/08/01 21:15:33]

Done.

+
+    // The payload associated with the message, if any.
+    DOMString payload;
+  };
+
+  interface Events {
+    // Fired when a push message has been received.
+    // |message| : The details associated with the message.
+    static void onMessage(Message message);
+  };
+};