Add support for creating bluetooth RFCOMM sockets.

chrome/browser/chromeos/bluetooth/bluetooth_socket.h

+// 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.
+
+#ifndef CHROME_BROWSER_CHROMEOS_BLUETOOTH_BLUETOOTH_SOCKET_H_
+#define CHROME_BROWSER_CHROMEOS_BLUETOOTH_BLUETOOTH_SOCKET_H_
+#pragma once
+
+#include <string>
+
+#include "base/memory/weak_ptr.h"
+
+namespace chromeos {
+
+class BluetoothDevice;
+
+// The BluetoothSocket class represents a socket to a specific service on
+// a BluetoothDevice.
+class BluetoothSocket : public base::SupportsWeakPtr<BluetoothSocket> {
+ public:
+  BluetoothSocket(BluetoothDevice *device, const std::string &service_uuid,
+      int id);

[keybuk, 2012/04/16 22:25:36]

nit: "* " and "& " not " *" and " &"

Public constructor suggests it's ok to instantiate these directly, rather than
going through BluetoothDevice.

Maybe better to have a private constructor and make BluetoothDevice a friend?

What is "id" ?

+  virtual ~BluetoothSocket() {}
+
+  // The id of this socket.
+  int id() const { return id_; }

[keybuk, 2012/04/16 22:25:36]

What is id? I tend to dislike arbitrary lookup types.

Is this the file descriptor? It should just be named as such

+
+  // Close this socket connection.
+  void Close();

[keybuk, 2012/04/16 22:25:36]

RAII: Close should be the destructor.

+
+ private:
+  BluetoothDevice* device_;
+  const std::string service_uuid_;
+  const int id_;

[keybuk, 2012/04/16 22:25:36]

Is this going to be derivable? How will we deal with the differences between
RFCOMM and L2CAP?

+
+  DISALLOW_COPY_AND_ASSIGN(BluetoothSocket);
+};
+
+}  // namespace chromeos
+
+#endif  // CHROME_BROWSER_CHROMEOS_BLUETOOTH_BLUETOOTH_SOCKET_H_