Heads up: bluetoothd on-demand startup

[Lennart Poettering]

On Fri, 12.06.09 23:27, Bastien Nocera (bnocera at redhat.com) wrote:

> 
> On Fri, 2009-06-12 at 23:58 +0200, Lennart Poettering wrote:
> > On Fri, 12.06.09 22:17, Bastien Nocera (bnocera at redhat.com) wrote:
> > 
> > > > > No, there's no service activation support. Would it be useful?
> > > > 
> > > > I think it would. Seems to me as if some of the BT functionality
> > > > (org.bluez.Manager, ...) might be useful even without having hw
> > > > plugged in.
> > > 
> > > All the API in doc/manager-api.txt shows that org.bluez.Manager's sole
> > > purpose is to tell you about available Adapters, and enumerate them.
> > > It's useless without an adapter plugged in.
> > 
> > Hmm, but what about the "any" object which provides org.bluez.Service?
> 
> What would you use that for? Check for a particular service (such as the
> audiosink, etc.) being available? Do you do something special when that
> happens? Wouldn't the devices just be invisible to PA in that case?

I was more thinking of installing some SDP data or so. Not that I'd
have any particular need for that right now, but that's what the API
is for afaiu.

> If we wanted to add support for dbus activation, we'd also need to
> implement a way to close ourselves if no dbus connection were made in a
> certain amount of time.

Yes, you'd have to count both clients and BT adapters, then.

Lennart

-- 
Lennart Poettering                        Red Hat, Inc.
lennart [at] poettering [dot] net
http://0pointer.net/lennart/           GnuPG 0x1A015CC4