Re: [Bluez-devel] D-Bus interfaces

Fredrik Noring
2004-02-11T12:32:56Z

Marcel,

mån 2004-02-09 klockan 11.38 skrev Marcel Holtmann:
> The goal is to have an interface that can be used by Gnome, KDE etc.
> without any proper knowledge of the running implementations and its
> configuration files. So this is not about hcid, this is about what do
> the UI applications need.

It's important for the Gnome applications to be able to do both
configuration and device management. These are two separate things.

Configuration management is about the persistent configurations
(past and present), basically those configrations stored in hcid.conf.
The Gnome applications must be able to list, add, remove and modify
such configurations.

There may exist configurations for devices that are not attached, and
there may also be devices attached that do not have any specific
configuration. The Gnome applications must be able to deal with these
kinds of situations intelligently.

Device management is about the devices currently attached, basically
a light version of the HCI functionality in the Bluetooth lib. The
Gnome applications should be able to list, probe and control such
devices, but probably only at a very basic/high level through DBus.

Your idea of having device managment in "org.bluetooth.hci" is good,
I think. However, we will have to decide on what that interface looks
like, because as noted in my previous e-mail, the HCI is not straight
forward for a DBus interface. Many things are too low-level.

The configuration management is probably better suited for another
interface, possibly "org.bluetooth.conf".

Name caches, pairing etc. also have several requirements to address.
For example, requesting a pairing procedure is a typical device management
task. But managing paired devices (listing, removing etc.) is typically a
configuration management kind of thing.

Comments?

Fredrik