Skip to contentSkip to conversation

The new D-Bus API specification

Bluez-devel Marcel Holtmann 3 participants 5 messages Feb 22, 2006 – Mar 4, 2006 Bluetooth drivers

lore
Share & tools
lore

Marcel Holtmann

author maintainer
#0 lore raw

Hi,

there have been rumors about a written API specification for the D-Bus interface of hcid (and bluetoothd in the future) and all of them is actually true. You will find the current version under hcid/dbus-api.txt inside the bluez-utils CVS. This isn't the final version, but it really looks good and something about 90% has been implemented in the last few weeks. Most of the work has been done by Claudio, Eduardo and Johan. So thank these guys for their work.

I like to see the rest 10% implemented and after that my plan is to release the next version of bluez-utils and open it for wider testing, but any feedback at this point is highly welcome. And I also like to see sample programs in various languages that we can include for reference.

Regards

Marcel

-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

author maintainer
#1 lore raw

Hi,

Quoted 8 lines

there have been rumors about a written API specification for the D-Bus interface of hcid (and bluetoothd in the future) and all of them is actually true. You will find the current version under hcid/dbus-api.txt inside the bluez-utils CVS. This isn't the final version, but it really looks good and something about 90% has been implemented in the last few weeks. Most of the work has been done by Claudio, Eduardo and Johan. So thank these guys for their work.

Quoted 4 lines

I like to see the rest 10% implemented and after that my plan is to release the next version of bluez-utils and open it for wider testing, but any feedback at this point is highly welcome. And I also like to see sample programs in various languages that we can include for reference.

there has been some more progress and a small update to the D-Bus API document. The current CVS contains the latest version which includes also a dbus-test script written in Python. The local device name and minor device class are now stored on the filesystem and remembered after reboot.

Please review the API document and send in comments. We also need a more secure D-Bus service config file.

Regards

Marcel

-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

#2 lore raw

Hi Marcel,

I tested the latest bluez-utils CVS version with the recent D-Bus changes and I have some comments:

* Policy
I'm not sure, but I think some linux distributions use pam_console instead of at_console. We sould investigate more to avoid future problems. Another thing are the rules. at_console aims provide a way to refer to users that are not physically sitting in front of the computer. I tested send D-Bus messages from the local host or connected through ssh and I didn't noticed differences. I mean, the behaviour is the same. Remote users still able to send D-Bus messages.

* Device->Adapter
Maybe should be better if we rename the function names and constants too. Or remove the prefix "dev" and "DEV". These prefixes were added to avoid confusion when all functions were in the same file.

* Error
I noticed that there are different handling of hci_open_dev result.
I found bluez_new_failure_msg and error_no_such_device calls to handle the same error. I will send a patch to use the same approach.

Regards,
Claudio.

Quoted 5 lines · Marcel Holtmann

Hi,

Quoted 3 lines

there have been rumors about a written API specification for the D-Bus interface of hcid (and bluetoothd in the future) and all of them is actually true. You will find the current version under hcid/dbus-api.tx=

t

Quoted 8 lines
Quoted 8 lines

inside the bluez-utils CVS. This isn't the final version, but it really looks good and something about 90% has been implemented in the last few weeks. Most of the work has been done by Claudio, Eduardo and Johan. So thank these guys for their work.

I like to see the rest 10% implemented and after that my plan is to release the next version of bluez-utils and open it for wider testing, but any feedback at this point is highly welcome. And I also like to se=

e

Quoted 13 lines
Quoted 1 line

sample programs in various languages that we can include for reference.

there has been some more progress and a small update to the D-Bus API document. The current CVS contains the latest version which includes also a dbus-test script written in Python. The local device name and minor device class are now stored on the filesystem and remembered after reboot.

Please review the API document and send in comments. We also need a more secure D-Bus service config file.

Regards

Quoted 7 lines

Marcel

-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting langua=

ge

Quoted 1 line

that extends applications into web and mobile media. Attend the live webc=

ast

Quoted 1 line

and join the prime developer group breaking into this new coding territor=

y!

Quoted 1 line

http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat=

=3D121642

Quoted 5 lines

_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

--
---------------------------------------------------------
Claudio Takahasi
Instituto Nokia de Tecnologia - INdT

-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

author maintainer
#3 lore raw

Hi Claudio,

Quoted 11 lines

I tested the latest bluez-utils CVS version with the recent D-Bus changes and I have some comments:

* Policy
I'm not sure, but I think some linux distributions use pam_console instead of at_console. We sould investigate more to avoid future problems. Another thing are the rules. at_console aims provide a way to refer to users that are not physically sitting in front of the computer. I tested send D-Bus messages from the local host or connected through ssh and I didn't noticed differences. I mean, the behaviour is the same. Remote users still able to send D-Bus messages.

actually the at_console should be transparent between different Linux distributions. However we need to verify that it works on at least Fedora, SuSE, Debian and Ubuntu.

Quoted 4 lines

* Device->Adapter
Maybe should be better if we rename the function names and constants too. Or remove the prefix "dev" and "DEV". These prefixes were added to avoid confusion when all functions were in the same file.

Remove the prefix completely, because it is all internal.

Quoted 4 lines

* Error
I noticed that there are different handling of hci_open_dev result.
I found bluez_new_failure_msg and error_no_such_device calls to handle the same error. I will send a patch to use the same approach.

Go ahead and send fixed. I am to busy to fully complete that change.

Regards

Marcel

-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

#4 lore raw
Quoted 14 lines · Marcel Holtmann

Hi Claudio,

Quoted 11 lines

I tested the latest bluez-utils CVS version with the recent D-Bus changes and I have some comments:

* Policy
I'm not sure, but I think some linux distributions use pam_console instead of at_console. We sould investigate more to avoid future problems. Another thing are the rules. at_console aims provide a way to refer to users that are not physically sitting in front of the computer. I tested send D-Bus messages from the local host or connected through ssh and I didn't noticed differences. I mean, the behaviour is the same. Remote users still able to send D-Bus messages.

Quoted 3 lines

actually the at_console should be transparent between different Linux distributions. However we need to verify that it works on at least Fedora, SuSE, Debian and Ubuntu.

at_console currently doesn't work on Debian, but does on Ubuntu (using pam-foreground not pam_console). However i intend to add pam-foreground support to debian's dbus too, which would make at_console supported on debian too.

Sjoerd

Signature · 1 line
The moon may be smaller than Earth, but it's further away.