Re: [Bluez-devel] D-Bus interfaces

Marcel Holtmann
2004-02-09T15:46:09Z

Hi Fredrik,

> > this is only true if the plain file itself is designed in somekind of
> > database format like /etc/passwd, but for hcid.conf that is not
> > acceptable. The format of hcid.conf is more flexible and if a user has
> > to edit this file, I don't wanna allow a program do edit it as well and
> > introduce its own format style.
>
> Why is the formating style a problem?

ask yourself what's the indentation of hcid.conf and how should a
computer program know about it. Of course this is possible to handle,
but it is always a mess.

> > So we have to separate some settings.
>
> Is the formating style issue the main reason for introducing a binary
> database instead of plain text?

No. This is the reason against letting hcid modify the hcid.conf. If the
settings are stored like in /etc/passwd or in a per-line basis I have no
problems with plain text files for this case.

> > If we want a clean interface for the configuration stuff that is not
> > covered by the HCI specification (like name cache etc.) we must go
> > through these interface in all cases, because the hcid implementation is
> > replaceable and the storage format also.
>
> It would be great to have file storage documented and part of the interface
> as well. Forcing specialized tools isn't flexible and user/admin friendly.

No. If we use a uniform storage, there is no need for a D-Bus interface,
because the application can modify the storage directly. One of the main
ideas is to abstract from the storage of the information. We provide an
interface to access and modify them and that must be enough.

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.