From: sathish <sathish.n@globaledgesoft.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: metadata dbus
Date: Tue, 29 Nov 2011 17:52:44 +0530 [thread overview]
Message-ID: <4ED4CE94.7060002@globaledgesoft.com> (raw)
In-Reply-To: <CABBYNZKGPhwrEd7bhGvP2JUUfauXXcqoHZeg4DZf1dbuuQinMA@mail.gmail.com>
On Tuesday 29 November 2011 05:30 PM, Luiz Augusto von Dentz wrote:
> Hi Sathish,
>
> On Tue, Nov 29, 2011 at 1:39 PM, sathish<sathish.n@globaledgesoft.com> wrote:
>> Hi Luiz,
>> The bluez that is in git repository has the dbus api saying something
>> about metadata information , will that dbus api will be useful
> I suppose you are talking about org.bluez.MediaPlayer? This interface
> is implemented by other processes (players) to expose their metadata,
> IMO it is not really suitable for the opposite role. I would suggest
> having another interface specific for this role (e.g. org.bluez.Target
> or org.bluez.Player) which gonna be registered in the device object
> path, it should be pretty similar to MediaPlayer interface except for
> Release. It also a good idea to think about how we gonna address
> multiple players since that is supported in AVRCP 1.4.
>
Hi Luiz,
Thanks for the kind reply. Will these interface gives metadata
information about all players or players that support mpris.
--
Thanks& Regards,
Sathish N
next prev parent reply other threads:[~2011-11-29 12:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 9:27 metadata dbus sathish
2011-11-29 11:26 ` Luiz Augusto von Dentz
2011-11-29 11:39 ` sathish
2011-11-29 12:00 ` Luiz Augusto von Dentz
2011-11-29 12:22 ` sathish [this message]
2011-11-29 13:43 ` FTP file authorization and transfer progress support Jaganath
2011-11-29 13:53 ` Johan Hedberg
2011-11-29 14:16 ` Luiz Augusto von Dentz
2011-11-30 6:34 ` Jaganath
2011-11-30 6:45 ` Brian Gix
2011-11-30 6:50 ` Hendrik Sattler
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=4ED4CE94.7060002@globaledgesoft.com \
--to=sathish.n@globaledgesoft.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).