[Bluez-devel] Bonding methods only avaliable for present adapters

[Bluez-devel] Bonding methods only avaliable for present adapters

[Daniel Gollub]

Hi,

i started porting the kcm_btpaired module (KDE controlcenter menu) to make use 
of the BlueZ DBus API. The kcm_btpaired module is intended to 
view/list/delete/export/... linkkeys of remote devices. The bonding methods 
(and other adapter specifics methods ..) can only used when the adapter is 
present. So the linkkey list in kcm_btpaired will be empty, when there is no 
bluetooth dongle connected. 

Is this intended in the DBus API? That methods, which are based on stored 
data, not avaliable?

If not, maybe a new object path for known devices would be helpful. 
Like: /org/bluez/FF:FF:FF:FF:FF or /org/bluez/adapters/FF:FF:FF:FF:FF

Which should provide near the same methods as a present adapter.  At least the 
function which based on stored stuff from /var/lib/bluetooth/*/*
Maybe this can also be done with the org.bluez.Adapter interface.

Other suggestions? 
Or is direct access to linkkeys via filesystem the only way?

best regards,
Daniel

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Bonding methods only avaliable for present adapters

[Marcel Holtmann]

Hi Daniel,

> i started porting the kcm_btpaired module (KDE controlcenter menu) to make use 
> of the BlueZ DBus API. The kcm_btpaired module is intended to 
> view/list/delete/export/... linkkeys of remote devices. The bonding methods 
> (and other adapter specifics methods ..) can only used when the adapter is 
> present. So the linkkey list in kcm_btpaired will be empty, when there is no 
> bluetooth dongle connected. 
> 
> Is this intended in the DBus API? That methods, which are based on stored 
> data, not avaliable?

actually we never really thought about it. In most cases you only want
to modify device settings for attached devices.

> If not, maybe a new object path for known devices would be helpful. 
> Like: /org/bluez/FF:FF:FF:FF:FF or /org/bluez/adapters/FF:FF:FF:FF:FF
> 
> Which should provide near the same methods as a present adapter.  At least the 
> function which based on stored stuff from /var/lib/bluetooth/*/*
> Maybe this can also be done with the org.bluez.Adapter interface.

It would be an option to allow additional access for currently not
present adapters. I am not sure if that is really needed in the real
world.

> Or is direct access to linkkeys via filesystem the only way?

The storage and storage format should be hidden from all desktop
application. Remember that there should not even be any need to link
against the Bluetooth library.

Regards

Marcel



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel