public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Elvis Pfützenreuter" <elvis.pfutzenreuter@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] bluetoothd D-Bus interface proposals(draft 00.05)
Date: Fri, 19 Aug 2005 14:27:48 -0300	[thread overview]
Message-ID: <8c9e090508191027e4646f1@mail.gmail.com> (raw)
In-Reply-To: <9307f5f2050818135877575293@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2131 bytes --]

> Probably my poor english caused some misunderstanding, the address
> *IS* part of the object path already, I can handle several adapters
> without any problems right now, and every adapter has a path like
> /org/bluetool/<BDADDR>/device


Maybe even the "device" word in the path is unnecessary, since the address 
implies the notion of an adapter? Also, if you want to support multiple BT 
adapters, there could be a "default" path (independent of the address) so 
most applications would just use that instead of first finding the mac 
addresses of the adapters... How many machines in the world have more than 1 
adapter? :) 


if the property is not a string or the parameters are not bytes, an
> exception is thrown by the dbus wrapper (see the 'try' block at the
> beginning?) and I send an error message back to the caller explaining
> the error, otherwise everything goes on linearly
> 
> What the "database" does (this database is not sdpd, it's an object
> created by the bluetool daemon), is simply to find what "helpers" are
> installed (ie: reading a list from a configuration file) and execute
> them, not much more actually :) every helper in turn registers its own
> object path and waits


So, as I could understand, you would use one process per profile, and the 
main deamon would forward orders via DBUS to these 'slaves'?

Another thing, will all these deamons be integrated into bluez-utils? Or it 
would be an independent BT deamon initiative? Which would be the dependency 
relationship with bluez-utils, and other libraries like, possibly, glib?

A last comment (given that my DBUS knowledge is poor) would be that throwing 
all interfaces on the same object turns more difficult to the clients to 
identify which services are available (they would have to use some form of 
interface introspection (which is probably more boring than just scanning 
the object namespace?). Also, I don't know if it is possible to turn on/turn 
off some interface on an object at will during runtime - registering and 
unregistering an object I know it is quite easy :P
--
Elvis

[-- Attachment #2: Type: text/html, Size: 2556 bytes --]

  reply	other threads:[~2005-08-19 17:27 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-16 21:15 [Bluez-devel] bluetoothd D-Bus interface proposals(draft 00.05) Claudio Takahasi
2005-08-16 22:45 ` P. Durante
2005-08-18 12:05   ` Claudio Takahasi
2005-08-18 20:58     ` P. Durante
2005-08-19 17:27       ` Elvis Pfützenreuter [this message]
2005-08-22 11:17         ` Marcel Holtmann
2005-08-22 12:04           ` Elvis Pfützenreuter
2005-08-22 12:27             ` Claudio Takahasi
2005-08-22 12:37               ` Peter Robinson
2005-08-22 12:51                 ` Claudio Takahasi
2005-08-22 14:26                   ` P. Durante
2005-08-22 14:34                     ` Marcel Holtmann
2005-08-22 17:39                       ` Claudio Takahasi
2005-08-22 17:50                         ` Marcel Holtmann
2005-08-22 19:47                           ` Claudio Takahasi
2005-08-29 21:13                             ` Claudio Takahasi
2005-08-29 21:46                               ` Marcel Holtmann
2005-08-30 10:07                                 ` Paul Hedderly
2005-08-30 13:14                                 ` Claudio Takahasi
2005-08-30 18:16                                   ` Claudio Takahasi
2005-09-01  9:57                                     ` Marcel Holtmann
2005-08-22 14:29                 ` Marcel Holtmann
2005-08-22 14:27               ` Marcel Holtmann
2005-08-22 14:21             ` Marcel Holtmann

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=8c9e090508191027e4646f1@mail.gmail.com \
    --to=elvis.pfutzenreuter@gmail.com \
    --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