Re: [Bluez-devel] D-Bus interfaces

[Marcel Holtmann <marcel@holtmann.org>]

Hi Fredrik,

> > this actually depends on what you provide. The httpd provides the
> > implementation of the HTTP. We will provide a general and extend
> > interface to the HCI functions, so we call it "hci". The hcid is the
> > implementation of these functions on the server side.
> 
> For example saving/loading the hcid configuration file (hcid.conf) isn't 
> about HCI functions, is it? To include such out-of-HCI-scope functions, 
> hcid should probably export interfaces beyond the HCI space:

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.
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.

> Can I ask you to provide a list of all the standard HCI functions? Is
> the syntax/parameters/semantics defined so that exactly one HCI interface
> implementation makes sense?

The HCI is well defined in the Bluetooth specification and you can of
course look at libs2. The source contains all defined HCI commands and
events for Bluetoth 1.2.

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.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel