Re: [Bluez-devel] D-Bus interfaces

[Marcel Holtmann <marcel@holtmann.org>]

Hi Fredrik,

> Here are some basic requirements, I think, for a Gnome Bluetooth Configuration
> tool:
> 
>    1. List devices currently attached.
>    2. Get info on devices currently attached (address, name, manufacturer,
>       type etc.)

Agreed.

But I also think that we should make is possible to list and configure
previous attached devices. So they can change settings and attach the
device later.

>    3. Permanently configure device status (up/down).

Agreed. Put "reset" to this list.

Maybe a flag for auto-up on/off per device would be nice.

>    4. Permanently configure device name.
>    5. Permanently configure device discoverability (Iscan? Pscan? Which?)

Agreed.

>    6. Permanently configure pair mode (allow/disallow).

I don't think that we need that. The pairing mode from hcid can go away
and we should use multi every time.

If a specific service like PAN requests a pairing or not is out of scope
for the current interface. These a service specific settings.

>    7. List permanently stored configurations.
>    8. Remove permanently stored configurations.

What do you mean by permanently stored configurations?

>    9. List devices which are paired.
>   10. Remove devices which are paired.

Agreed.

>   11. Request the name for a device address, if available in the name cache.

Agreed.

But we also need a method to set an alias name for a remote device.

>   12. Perform av device scan (this will also update the name cache).

We need something, but I am not sure how to do this. Let's put it at the
bottom of the list.

Don't worry about the name cache. That is a very easy task for hcid.

>   13. Perform a pairing procedure (will update the name cache too).
>   14. Provide a one-time PIN during a pairing procedure.

The pairing procedure should work in background and if a PIN is needed a
PIN helper window should be opened. Maybe you should look at the
bluez-pin program on the internet and the D-Bus extensions for hcid.

The one-time PIN method is what I really want to have. So an application
can provide a previous entered PIN and send it to hcid. The hcid will
use this for the next PIN request (and don't call a PIN helper) and then
forget the PIN.

> (1) and (2) can possibly be solved without DBus, but the rest will require it.

It is possible, but we won't have it. D-Bus for everything ;)

Regards

Marcel




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel