Hi Fredrik,
I sent a lot of emails about bluetoothd specification, but I didn't
receive enough feedbacks. bluetoothd will be the main entity
responsible to handle user requests(connections, device setup,
security, ...).
Currently, we are working on hcid D-Bus services. hcid is our
playground for validate some ideas. I developed a internal version
of the bluetoothd, but I need align with bluez community and
use the new communication interface (between kernel and the userspace)
that is being developed.
There is docs about bluetoothd available at:
http://www.cin.ufpe.br/~ckt/bluez
Your feedback is welcome!
Regards,
Claudio.
Hi Fredrik,
> > the idea is not bad, but it will never work this way. This is because
> > how the Bluetooth security architecture is designed. We need a central
> > root service that deals with the kernel side of HCI. However the control
> > of pairing etc. for users will be handled over D-Bus.
>
> Ah. Is there any documentation on how this D-BUS interface works?
Claudio has written something, but nothing is written in stone.
Regards
Marcel
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel