From: Claudio Takahasi <cktakahasi@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] bluetoothd D-Bus interface proposals(draft 00.05)
Date: Mon, 22 Aug 2005 09:27:10 -0300 [thread overview]
Message-ID: <e1effdeb0508220527500878ab@mail.gmail.com> (raw)
In-Reply-To: <8c9e090508220504100c127e@mail.gmail.com>
Hi folks,
It's possible register multiple D-Bus object paths. My suggestion=20
for handle multiple adapters is register a default path and paths
based on the device address.=20
eg: suppose two adapters(11:22:33:44:55:66, 77:88:99:00:11:22)
The possible paths are:
/org/bluez/bluetoothd/hci (default path - first adapter)
/org/bluez/bluetoothd/112233445566/hci (first adapter)
/org/bluez/bluetoothd/778899001122/hci (second adapter)
/org/bluez/bluetoothd/pan (default path - first adapter)
/org/bluez/bluetoothd/112233445566/pan (first adapter)
/org/bluez/bluetoothd/778899001122/pan (second adapter)
...
The service to list the adapter must be moved to the main path
(/org/bluez/bluetoothd) or to a new one /org/bluez/bluetoothd/devices.
The message handle function will become more complex, but I don't
see other solution.
Regards,
Claudio.
On 8/22/05, Elvis Pf=FCtzenreuter <elvis.pfutzenreuter@gmail.com> wrote:
>=20
> =20
> > this is a wrong argument. The case with only one adapter is the special
> > case. Multiple adapters are default.
>=20
> You mean, e.g. a computer with multiple dongles?=20
> =20
>=20
>
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-08-22 12: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
2005-08-22 11:17 ` Marcel Holtmann
2005-08-22 12:04 ` Elvis Pfützenreuter
2005-08-22 12:27 ` Claudio Takahasi [this message]
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=e1effdeb0508220527500878ab@mail.gmail.com \
--to=cktakahasi@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