public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] pand D-Bus service
Date: Mon, 11 Jul 2005 21:27:14 +0200	[thread overview]
Message-ID: <1121110034.5934.24.camel@notepaq> (raw)
In-Reply-To: <e1effdeb050711115470809e4a@mail.gmail.com>

Hi Claudio,

> According with your emails, bluetoothd shall provide 
> methods for settings and send signals.
> I finished the D-Bus services for pand, now we need
> define how organize these services. 
> 
> In my opinion the bluetoothd should be responsible for
> provide all D-Bus services, including pand, hidd, cip, ...
> Create D-Bus services for each daemon will require 
> monitor a lot of dbus connections. It's easier and more
> efficient create "profile objects" for each profile inside
> bluetoothd. Buetoothd can monitor different interfaces and 
> objects.

this is my idea and then you can write a simple Python script and use
all Bluetooth stuff over D-Bus. This way it should be possible to
implement some graphical tools for using Bluetooth.

> Currently, my D-Bus pand implementation is providing:
>   -adapters: show local bluetooth adapters
>   -connect:connect to a bluetooth device
>   -connections: show active connections
>   -disconnect: kill connections
>   -enable-bridge: enable automatic bridge creation on listening
>   -find: search for a service
>   -listen: start/stop listen for bluetooth connections
>   -role: switch the role MASTER|SLAVE
>   -udhcp:enable UDHCP on listen or connect
>   -init: initialize the bluez pan daemon (pand)
>   -kill: kill the pand
> 
> 
> If you see the code of D-Bus hcid, the D-Bus message control functions
> are similar. The best approach is move all to daemon directory.

The bluetoothd should handle every of these things. However the main
focus at the moment is device configuration and the handling of security
related stuff. I am not 100% sure about the interface, but in general I
like to use something similar to Hal.

Adding interfaces for PAN, HID etc. is not so important for me. Once we
have the core stuff running, the should be really easy then.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP, 
AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-07-11 19:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-08 18:37 [Bluez-devel] pand D-Bus service Claudio Takahasi
2005-07-08 19:08 ` Marcel Holtmann
2005-07-11 18:54   ` Claudio Takahasi
2005-07-11 19:27     ` Marcel Holtmann [this message]
2005-07-11 20:16       ` Claudio Takahasi
2005-07-11 21:26         ` Marcel Holtmann
2005-07-12 17:07           ` Claudio Takahasi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1121110034.5934.24.camel@notepaq \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox