bluetooth: Add device list retrieval for chrome://bluetooth-internals

device/bluetooth/public/interfaces/adapter.mojom

Index: device/bluetooth/public/interfaces/adapter.mojom
diff --git a/device/bluetooth/public/interfaces/adapter.mojom b/device/bluetooth/public/interfaces/adapter.mojom
new file mode 100644
index 0000000000000000000000000000000000000000..e46e7a9b89ed12953058d31d1649cb3b4e2cd33f
--- /dev/null
+++ b/device/bluetooth/public/interfaces/adapter.mojom
@@ -0,0 +1,30 @@
+// 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 bluetooth.mojom;
+
+struct DeviceInfo {
+  string? name;
+  string name_for_display;
+  string id;
+  string address;
+};
+
+interface Adapter {
+  // Retrieves the list of the devices known by the adapter including Connected
+  // Devices, GATT Connected Devices, Paired Devices and Devices discovered
+  // during a classic or low-energy scan.
+  GetDevices() => (array<DeviceInfo> devices);

[dcheng, 2016/09/30 07:04:06]

My main question here is whether it'd make sense to just have a Device
interface. I'm not sure how AdapterClient is going to be implemented in a
followup, but I'm guessing we're going to be doing lookup by the DeviceInfo? If
so, would it make more sense to just transfer a mojo handle to the Device
interface and eliminate/simplify the lookup?

+
+  // Sets the client that listens for the adapter's events.
+  SetClient(AdapterClient client);

[dcheng, 2016/09/30 07:04:06]

Can we add this (and AdapterClient) in the CL where they're actually implemented
and used?

[scheib, 2016/09/30 16:52:42]

Fair point, but at this point in review I don't think it's worth splitting out.
This patch establishes the boilerplate for the Adapter interface and its client,
including the client doesn't bloat it that much and was important to figure out
the context for the bindings.

+};
+
+interface AdapterClient {
+  // Called the first time a device is discovered.
+  DeviceAdded(DeviceInfo device);
+
+  // Called after the device hasn't been seen for 3 minutes.
+  DeviceRemoved(DeviceInfo device);
+};