chrome: bluetooth: hook up DeviceCreated/Removed signals

chrome/browser/chromeos/dbus/bluetooth_adapter_client.h

Index: chrome/browser/chromeos/dbus/bluetooth_adapter_client.h
diff --git a/chrome/browser/chromeos/dbus/bluetooth_adapter_client.h b/chrome/browser/chromeos/dbus/bluetooth_adapter_client.h
index 73aaee2bf3bdf8d32c2b3cd05eb482ceb3d47ac4..33dd57db557677a560b64eedef21d31eee78f446 100644
--- a/chrome/browser/chromeos/dbus/bluetooth_adapter_client.h
+++ b/chrome/browser/chromeos/dbus/bluetooth_adapter_client.h
@@ -27,6 +27,14 @@ class BluetoothAdapterClient {
    public:
     virtual ~Observer() {}
 
+    // Called when a new known device has been created.
+    virtual void DeviceCreated(const std::string& adapter_path,
+                               const std::string& object_path) {}

[mukesh agrawal, 2012/02/01 00:48:42]

i'm somewhat surprised that these have default implementations. (i would have
expected Observer to be an abstract base.)

but it is consistent with the existing code, so i'll leave it up to you whether
or not to change.

[satorux1, 2012/02/01 17:45:18]

I think it's not so uncommon for observers to have default implementations, as
not all observers are interested in all events (i.e. with default
implementations, they can only implement events they are interested in).

+
+    // Called when a previously known device is removed.
+    virtual void DeviceRemoved(const std::string& adapter_path,
+                               const std::string& object_path) {}
+
     // Called when the adapter's Discovering property changes.
     virtual void DiscoveringPropertyChanged(const std::string& object_path,
                                             bool discovering) {}