Implement BroadcastChannel

components/webmessaging/public/interfaces/broadcast_channel.mojom

Index: components/webmessaging/public/interfaces/broadcast_channel.mojom
diff --git a/components/webmessaging/public/interfaces/broadcast_channel.mojom b/components/webmessaging/public/interfaces/broadcast_channel.mojom
new file mode 100644
index 0000000000000000000000000000000000000000..fbb70af8a387a3dc3ae67bd14f94cae4f58b4fdc
--- /dev/null
+++ b/components/webmessaging/public/interfaces/broadcast_channel.mojom
@@ -0,0 +1,24 @@
+// Copyright 2016 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.
+
+module webmessaging.mojom;
+
+import "url/mojo/origin.mojom";
+
+interface BroadcastChannelClient {
+  // Messages are passed as SerializedScriptValue.
+  OnMessage(string message);
+};
+
+interface BroadcastChannelService {

[Ken Rockot(use gerrit already), 2016/06/24 18:14:51]

I should have caught this earlier, but please don't add a "Service" suffix to
new mojo interfaces. In general we'd like to keep some consistent terminology
moving forward and "service" is reserved for aggregated interface providers in
//services which might make sense to physically isolate from each other at
runtime (see //services/README.md).

Maybe BroadcastChannelProvider or BroadcastChannelConnector?

[Marijn Kruisselbrink, 2016/06/24 18:37:11]

Done

+  // Connect to the channel identified by the |origin| and |name|. Messages can
+  // be sent to the channel using |sender|, and messages to the channel will be
+  // received by |receiver|.
+  // All connections to channels made from the same event loop should be made
+  // through the same BroadcastChannelService to ensure correct ordering of
+  // messages.
+  ConnectToChannel(url.mojom.Origin origin, string name,
+                   associated BroadcastChannelClient receiver,
+                   associated BroadcastChannelClient& sender);
+};