757713 - B2G Bluetooth: Get adapter path

Status: RESOLVED DUPLICATE of bug 744349

(Core :: DOM: Device Interfaces, defect)

Description

[Eric Chou [:ericchou] [:echou]]

Low level function to get default BluetoothAdapter path.

Comment 1

[Eric Chou [:ericchou] [:echou]]

Attachment: WIP: still waiting for other patches checking in, feedback first

The adapter path is a string representing a BluetoothAdapter object. It's also one of parameters of all BluetoothAdapter related dbus functions.

Comment 2

[Kyle Machulis [:qdot] [:kmachulis] (INACTIVE)]

Comment on attachment 626313 [details] [diff] [review]
WIP: still waiting for other patches checking in, feedback first

Review of attachment 626313 [details] [diff] [review]:
-----------------------------------------------------------------

GetAdapterPath, which I'm assuming will actually be calling dbus's DefaultAdapter, is already part of the DBus Signal Handler patch at bug 744349 (check out the WIP I have over there already). Main reason I did that is because I needed an example of signal hookups and that seemed best. Also, the only thing that should need to call DefaultAdapter is BluetoothManager, since it will establish the Adapter objects, and for now I think we'll only have one object. BluetoothManager is a RawDBusConnection so it should have its own connection to the system bus already.

That said, we can break out the calling of the GetDefaultAdapterPath code there and land it first here, as signals requires the dbus node name, but not vice versa.

Comment 3

[Eric Chou [:ericchou] [:echou]]

OK, I'll mark this issue as a of bug 744349.

Comment 4

[Eric Chou [:ericchou] [:echou]]

OK, I'll mark this issue as a duplicate of bug 744349. I saw Kyle's WIP patch and I think that's what we want now.