linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Anderson Lizardo <anderson.lizardo@openbossa.org>,
	linux-bluetooth@vger.kernel.org
Subject: Re: [RFC BlueZ 3/3] core: Add Interfaces property to org.bluez.Device
Date: Wed, 07 Mar 2012 11:14:49 -0800	[thread overview]
Message-ID: <1331147689.3392.181.camel@aeonflux> (raw)
In-Reply-To: <CABBYNZK+Te2_dXweZ9xMPv8+ha9V9W_bLC2SuEpu7EQiinrFPw@mail.gmail.com>

Hi Luiz,

> >> > On Tue, Mar 6, 2012 at 8:07 AM, Luiz Augusto von Dentz
> >> > <luiz.dentz@gmail.com> wrote:
> >> >> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> >> >>
> >> >> This enables applications to be able to detect when an interface is
> >> >> enabled/disabled without depending on UUIDs.
> >> >> ---
> >> >>  doc/device-api.txt |    4 ++++
> >> >>  src/device.c       |   27 ++++++++++++++++++++++-----
> >> >>  2 files changed, 26 insertions(+), 5 deletions(-)
> >> >
> >> > I thought it was possible to achieve this by using D-Bus listeners?
> >> > E.g. similar to g_dbus_add_service_watch()
> >>
> >> Afaik there is no such thing as introspection data changed or anything
> >> like that, we could in theory have local listeners, but at least in
> >> BlueZ there is no much use for them since it is not really dynamic
> >> after drivers are loaded, but perhaps for oFono and others it could be
> >> useful to have some way to watch when interfaces changes.
> >>
> >> In case of oFono it does that by having e.g.
> >> ofono_modem_add_interface/ofono_modem_remove_interface.
> >>
> >> > What happens when the interface is unregistered with
> >> > g_dbus_unregister_interface() ?
> >>
> >> This should only be the case when removing the object so the driver
> >> .remove is called which then calls g_dbus_unregister_interface.
> >
> > I was not planning to add this to our gdbus code and focus on getting
> > this right for ELL. However look into the D-Bus ObjectManager
> > specification since that is what you want actually.
> 
> So the way forward is to implement ObjectManager? We could have that
> without breaking any API, but I guess it would make sense to change
> API such as the manager to take advantage of the ObjectManager.

have a look at ObjectManager and how much it takes for us to use it. I
know that the properties will be a bit of problem, but maybe still worth
it to start supporting it.

> Btw what is ELL?

http://git.kernel.org/?p=libs/ell/ell.git

Regards

Marcel



      parent reply	other threads:[~2012-03-07 19:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-06 12:07 [RFC BlueZ 1/3] gdbus: Add g_dbus_list_interfaces function Luiz Augusto von Dentz
2012-03-06 12:07 ` [RFC BlueZ 2/3] core: Add Interfaces property to org.bluez.Adapter Luiz Augusto von Dentz
2012-03-06 12:07 ` [RFC BlueZ 3/3] core: Add Interfaces property to org.bluez.Device Luiz Augusto von Dentz
2012-03-06 12:57   ` Anderson Lizardo
2012-03-06 13:26     ` Luiz Augusto von Dentz
2012-03-06 14:35       ` Marcel Holtmann
2012-03-07  8:14         ` Luiz Augusto von Dentz
2012-03-07 14:39           ` Vinicius Costa Gomes
2012-03-07 19:14           ` Marcel Holtmann [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=1331147689.3392.181.camel@aeonflux \
    --to=marcel@holtmann.org \
    --cc=anderson.lizardo@openbossa.org \
    --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).