Re: [Bluez-devel] D-Bus interfaces

Marcel Holtmann
2004-02-09T11:03:05Z

Hi Fredrik,

> > I don't wanna support this. The hcid.conf file is a configuration file
> > for a default configuration and don't needs to read or stored through
> > the D-Bus interface. All modifications done through the D-Bus must be
> > stored in another file/database. The goal is to have an interface that
> > can be used by Gnome, KDE etc. ...
>
> This doesn't make sense. What happens when a user edits hcid.conf
> manually? It's simpler and straight forward to have exactly one config
> file which also can be edited manually if required. Please note that
> Gnome will most likely not expose _all_ HCI configuration features and
> that manual editing will be required to use these.

I don't wanna support a config file which is intend to be editable by a
user and changable by a program. This is always a mess.

The hcid.conf will provide the default settings for new devices or
special settings that are not in the database. If a setting is in the
database, this one will be used. The hcid.conf can also contain features
which we don't provide over a D-Bus interface. I don't have any problems
if the Gnome utility don't provide support for all HCI config stuff. We
need to write a command line utility with full support anyway, because
the interface must be tested.

Regards

Marcel

-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.