All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Mikel Astiz <mikel.astiz.oss@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>,
	Mikel Astiz <mikel.astiz@bmw-carit.de>
Subject: Re: [RFC BlueZ v0 00/13] Add experimental org.bluez.Service1
Date: Mon, 6 May 2013 12:19:37 +0300	[thread overview]
Message-ID: <CABBYNZLQTOsdeJ52WF3pn_+bYqSeXjeK_6-TK3RhcXrS567_Ag@mail.gmail.com> (raw)
In-Reply-To: <1367829810-8262-1-git-send-email-mikel.astiz.oss@gmail.com>

Hi Mikel,

On Mon, May 6, 2013 at 11:43 AM, Mikel Astiz <mikel.astiz.oss@gmail.com> wrote:
> From: Mikel Astiz <mikel.astiz@bmw-carit.de>
>
> Beyond the desktop use-cases, some users (e.g. GENIVI) are interested in having profile-specific information and control interfaces exposed in D-Bus. Such APIs did exist in BlueZ 4 but were dropped for BlueZ 5 in favor of simpler API simplicity. This service-specific interfaces had a fairly low priority for BlueZ 5 and therefore the discussion was postponed.
>
> This patchset proposes org.bluez.Service1 as an attempt to cover these needs. As compared to the former Device.ConnectProfile()/DisconnectProfile(), the approach has the following advantages:
> - Multiple instances of the same UUID can be exposed.
> - The state of each service can be exposed, without hackish lists like Device.ConnectedProfiles.
> - It's ObjectManager-centric.
> - The design should scale better if new properties are required in the future (supported features, service handle, etc.)
>
> Mikel Astiz (13):
>   test: Remove obsolete test script
>   test: Add UUID alias table to bluezutils.py
>   test: Support human-friendly UUIDs in test-device
>   test: Show human-friendly UUIDs in list-devices
>   dbus: Add new org.bluez.Service1
>   dbus: Add Device property to org.bluez.Service1
>   dbus: Add UUID property to org.bluez.Service1
>   dbus: Add state property to org.bluez.Service1
>   dbus: Add Connect/Disconnect to org.bluez.Service1
>   doc: Add API documentation for org.bluez.Service1
>   dbus: Deprecate old profile-connecting API
>   test: Add test-service script
>   test: Add --uuid to test-service
>
>  Makefile.am         |   2 +-
>  Makefile.tools      |   2 +-
>  doc/device-api.txt  |   4 +-
>  doc/service-api.txt |  54 ++++++++++++++
>  src/device.c        |  14 ++--
>  src/service.c       | 197 +++++++++++++++++++++++++++++++++++++++++++++++++++-
>  src/service.h       |   2 +-
>  test/bluezutils.py  |  84 ++++++++++++++++++++++
>  test/list-devices   |   6 +-
>  test/simple-service | 128 ----------------------------------
>  test/test-device    |   4 +-
>  test/test-service   | 174 ++++++++++++++++++++++++++++++++++++++++++++++
>  12 files changed, 530 insertions(+), 141 deletions(-)
>  create mode 100644 doc/service-api.txt
>  delete mode 100755 test/simple-service
>  create mode 100755 test/test-service
>
> --
> 1.8.1.4

This is probably the way forward, but currently there have been some
instability after service was introduced, so before we move on to this
set I would like that we make sure those crashes are fixed.

--
Luiz Augusto von Dentz

  parent reply	other threads:[~2013-05-06  9:19 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-06  8:43 [RFC BlueZ v0 00/13] Add experimental org.bluez.Service1 Mikel Astiz
2013-05-06  8:43 ` [RFC BlueZ v0 01/13] test: Remove obsolete test script Mikel Astiz
2013-05-06  8:43 ` [RFC BlueZ v0 02/13] test: Add UUID alias table to bluezutils.py Mikel Astiz
2013-05-06  8:43 ` [RFC BlueZ v0 03/13] test: Support human-friendly UUIDs in test-device Mikel Astiz
2013-05-06  8:43 ` [RFC BlueZ v0 04/13] test: Show human-friendly UUIDs in list-devices Mikel Astiz
2013-05-06  8:43 ` [RFC BlueZ v0 05/13] dbus: Add new org.bluez.Service1 Mikel Astiz
2013-05-06  8:43 ` [RFC BlueZ v0 06/13] dbus: Add Device property to org.bluez.Service1 Mikel Astiz
2013-05-06  8:43 ` [RFC BlueZ v0 07/13] dbus: Add UUID " Mikel Astiz
2013-05-06  8:43 ` [RFC BlueZ v0 08/13] dbus: Add state " Mikel Astiz
2013-05-06 10:00   ` Luiz Augusto von Dentz
2013-05-07  7:49     ` Mikel Astiz
2013-05-06  8:43 ` [RFC BlueZ v0 09/13] dbus: Add Connect/Disconnect " Mikel Astiz
2013-05-06  8:43 ` [RFC BlueZ v0 10/13] doc: Add API documentation for org.bluez.Service1 Mikel Astiz
2013-05-15 16:38   ` Scott James Remnant
2013-05-16  6:22     ` Mikel Astiz
2013-05-16 17:10       ` Scott James Remnant
2013-05-17  9:20         ` Mikel Astiz
2013-05-06  8:43 ` [RFC BlueZ v0 11/13] dbus: Deprecate old profile-connecting API Mikel Astiz
2013-05-06  8:43 ` [RFC BlueZ v0 12/13] test: Add test-service script Mikel Astiz
2013-05-06  8:43 ` [RFC BlueZ v0 13/13] test: Add --uuid to test-service Mikel Astiz
2013-05-06  9:19 ` Luiz Augusto von Dentz [this message]
2013-05-15  8:56   ` [RFC BlueZ v0 00/13] Add experimental org.bluez.Service1 Mikel Astiz
2013-05-28  9:45     ` Mikel Astiz

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=CABBYNZLQTOsdeJ52WF3pn_+bYqSeXjeK_6-TK3RhcXrS567_Ag@mail.gmail.com \
    --to=luiz.dentz@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=mikel.astiz.oss@gmail.com \
    --cc=mikel.astiz@bmw-carit.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.