From: Johan Hedberg <johan.hedberg@gmail.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Quick question about org.bluez.Device and .audio.* Properties
Date: Tue, 22 Jul 2008 16:41:44 +0300 [thread overview]
Message-ID: <B6E47BE2-D488-41E1-A4DF-12D1B9E108A0@gmail.com> (raw)
In-Reply-To: <001f01c8eb58$d65ede10$6701a8c0@freqonedev>
Hi David,
On Jul 21, 2008, at 20:40, David Stockwell wrote:
> In the near-future 4.x, I understand that the org.bluez.audio.*
> interfaces will be attached to the existing Device, such that the
> object
> path (e.g.) /hci0/dev_* will have/export multiple DBus interfaces, not
> only org.bluez.Device but also org.bluez.audio.Control (could be
> multiple interfaces of the org.bluez.audio family). I also understand
> that the org.bluez.audio.* interfaces will be set up based on the SDP
> records in the host and remote when the connection/pairing is
> completed.
>
> Is my understanding of this accurate?
Yes.
> Second question: org.bluez.Device has a number of properties (e.g.,
> Connected) which are also valuable in the context of
> org.bluez.audio.*;
> should we duplicate the appropriate properties (and code) into the
> audio.* interface as well, or just require that anyone using wishing
> to
> access these properties address org.bluez.Device? Similarly, when a
> property changes, would we want to send the signal to a callback
> listening to .Device and .audio.*, or only to .Device?
The org.bluez.Device property relates only to the low-level ACL status
and not to any higher level connections. The audio service would have
it's own signals it sends based on the state of its L2CAP or RFCOMM
sockets or even higher level protocol states on top of the sockets.
Johan
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2008-07-22 13:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 17:40 [Bluez-devel] Quick question about org.bluez.Device and .audio.* Properties David Stockwell
2008-07-22 13:41 ` Johan Hedberg [this message]
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=B6E47BE2-D488-41E1-A4DF-12D1B9E108A0@gmail.com \
--to=johan.hedberg@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