bluetooth: Impl uses new WebBluetoothDevice in content/browser.

content/common/bluetooth/bluetooth_messages.h

Index: content/common/bluetooth/bluetooth_messages.h
diff --git a/content/common/bluetooth/bluetooth_messages.h b/content/common/bluetooth/bluetooth_messages.h
new file mode 100644
index 0000000000000000000000000000000000000000..799713adc8857425b2a5c9c0bbe3afb2b615a03c
--- /dev/null
+++ b/content/common/bluetooth/bluetooth_messages.h
@@ -0,0 +1,39 @@
+// Copyright 2014 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.
+
+// Messages for Web Bluetooth API.
+// Multiply-included message file, hence no include guard.
+
+#include "ipc/ipc_message_macros.h"
+#include "content/common/bluetooth/bluetooth_error.h"
+
+#define IPC_MESSAGE_START BluetoothMsgStart
+
+IPC_ENUM_TRAITS_MAX_VALUE(content::BluetoothError,
+                          content::BluetoothError::ENUM_MAX_VALUE)
+
+// Messages sent from the browser to the renderer.
+
+// Informs the renderer that the device request |request_id| succeeded.
+IPC_MESSAGE_CONTROL3(BluetoothMsg_RequestDeviceSuccess,
+                     int /* thread_id */,
+                     int /* request_id */,
+                     std::string /* instance_id */)
+
+// Informs the renderer that the device request |request_id| failed.
+IPC_MESSAGE_CONTROL3(BluetoothMsg_RequestDeviceError,
+                     int /* thread_id */,
+                     int /* request_id */,
+                     content::BluetoothError /* result */)
+
+// Messages sent from the renderer to the browser.
+
+// Requests a bluetooth device from the browser.
+IPC_MESSAGE_CONTROL2(BluetoothHostMsg_RequestDevice,

[Jeffrey Yasskin, 2014/11/24 23:30:12]

This file is probably the place to explain the security contracts across the IPC
boundary. For example, that RequestDevice is expected to open a chooser to let
the user pair a device with an origin. RequestDeviceSuccess indicates that
|instance_id| represents a device the origin has permission to use.

Is SetBluetoothMockDataSetForTesting blocked in any way outside of tests?

How does the browser figure out which origin is requesting access?

In terms of CONTROL vs ROUTED, the browser needs to be able to attach the
RequestDevice call to a particular RenderFrameHost, in order to attribute the
dialog to the right tab (or block it for iframes). How does that mapping get
made?

[scheib, 2014/11/25 16:11:06]

Done.
Not yet, issue created and commented. This shouldn't be harmful though.
This is deferred until later, I've now commented in code as such.

+                     int /* thread_id */,
+                     int /* request_id */)
+
+// Configures the mock data set in the browser used while under test.
+IPC_MESSAGE_CONTROL1(BluetoothHostMsg_SetBluetoothMockDataSetForTesting,
+                     std::string /* name */)