[Clean up] Expose ConnectToServiceInsecurely as a BluetoothDevice API on all platforms.

device/bluetooth/bluetooth_device.h

Index: device/bluetooth/bluetooth_device.h
diff --git a/device/bluetooth/bluetooth_device.h b/device/bluetooth/bluetooth_device.h
index 4557f3b5e0b795ca221ddea8f3ceaf08603c94e2..2f3a96b3edae3cbf62346ddb71a6458bcfebcbbb 100644
--- a/device/bluetooth/bluetooth_device.h
+++ b/device/bluetooth/bluetooth_device.h
@@ -356,6 +356,19 @@ class BluetoothDevice {
       const ConnectToServiceCallback& callback,
       const ConnectToServiceErrorCallback& error_callback) = 0;
 
+  // Attempts to initiate an insecure outgoing L2CAP or RFCOMM connection to the
+  // advertised service on this device matching |uuid|, performing an SDP lookup
+  // if necessary to determine the correct protocol and channel for the
+  // connection. Unlike ConnectToService, the outgoing connection will request
+  // no bonding rather than general bonding. |callback| will be called on a
+  // successful connection with a BluetoothSocket instance that is to be owned
+  // by the receiver. |error_callback| will be called on failure with a message
+  // indicating the cause.
+  virtual void ConnectToServiceInsecurely(
+    const device::BluetoothUUID& uuid,
+    const ConnectToServiceCallback& callback,
+    const ConnectToServiceErrorCallback& error_callback) = 0;

[armansito, 2014/10/15 19:02:16]

Kind of tangential to this CL, though I wonder why ConnectToServiceErrorCallback
doesn't return (in an argument) an enum ConnectErrorCode. It's strange that we
have different signatures for Connect and ConnectToService*. Perhaps add a TODO
for this, if what I'm saying makes sense to you.

[Ilya Sherman, 2014/10/15 22:04:45]

I personally find the strings more convenient than an enum, since most code that
handles connection failures doesn't really treat different failure reasons
differently, other than maybe logging the failure reason.  I'm therefore going
to omit the TODO, since I think it's worth discussing a bit more to figure out
what behavior we want, exactly.  In general, though, making Connect and
ConnectToService* have roughly the same signature makes sense to me.

+
   // Opens a new GATT connection to this device. On success, a new
   // BluetoothGattConnection will be handed to the caller via |callback|. On
   // error, |error_callback| will be called. The connection will be kept alive,