From: Johan Hedberg <johan.hedberg@gmail.com>
To: Anderson Lizardo <anderson.lizardo@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org,
Claudio Takahasi <claudio.takahasi@openbossa.org>
Subject: Re: [RFC BlueZ 7/7] doc: Add Register/Unregister GATT based services
Date: Tue, 24 Jul 2012 11:27:02 +0200 [thread overview]
Message-ID: <20120724092702.GA8706@x220.ice.intel.com> (raw)
In-Reply-To: <1343058920-18608-8-git-send-email-anderson.lizardo@openbossa.org>
Hi,
On Mon, Jul 23, 2012, Anderson Lizardo wrote:
> --- a/doc/service-api.txt
> +++ b/doc/service-api.txt
> @@ -43,6 +43,39 @@ Methods uint32 AddRecord(string record)
> org.bluez.Error.DoesNotExist
> org.bluez.Error.Failed
>
> + void Register(string uuid, dict settings,
> + array{object} characteristics)
> +
> + Add a GATT based service. The uuid represents the
> + primary/secondary service UUID. The settings
> + dictionary has the following format:
> + {
> + "id": string (optional)
> + }
> +
> + settings field is being added to allow API
> + flexibility. The "id" field allows the core to
> + manage handle allocation and internal GATT storage.
> +
> + GATT included services is supported by providing the
> + same characteristic object path (restricted to same
> + provider/owner).
> +
> + The characteristic objects implemented by the
> + caller shall follow the interface defined in the
> + attribute API.
> +
> + Possible errors: org.bluez.Error.InvalidArguments
> + org.bluez.Error.AlreadyExists
> +
> + void Unregister(string uuid)
> +
> + Removes a given GATT based service previously
> + registered by the caller.
> +
> + Possible errors: org.bluez.Error.InvalidArguments
> + org.bluez.Error.NotAuthorized
I don't think the Register/Unregister names are right since this is
purely LE/GATT specific. Or do you foresee this being used for
traditional (non-GATT) BR/EDR profiles? I'd either propose having a new
interface for these or then rename them (e.g. RegisterGATT?).
FWIW I'm also not sure that the interface name org.bluez.Service is
quite right. Interface names are supposed to describe something about
the object which implements them, but the object this interface is used
for (adapter) cannot be said to "be" a service. Instead, this interface
abstracts a local database of services. What would you think of calling
it ServiceManager or ServiceDatabase?
Johan
next prev parent reply other threads:[~2012-07-24 9:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 15:55 [RFC BlueZ 0/7] Generic GATT API changes Anderson Lizardo
2012-07-23 15:55 ` [RFC BlueZ 1/7] attrib-api: Remove local service hierarchy Anderson Lizardo
2012-07-23 15:55 ` [RFC BlueZ 2/7] attrib-api: Update introduction text Anderson Lizardo
2012-07-23 15:55 ` [RFC BlueZ 3/7] attrib-api: Remove GATT service hierarchy Anderson Lizardo
2012-07-23 15:55 ` [RFC BlueZ 4/7] attrib-api: Update Characteristic interface Anderson Lizardo
2012-07-23 15:55 ` [RFC BlueZ 5/7] attrib-api: Update Watcher interface methods Anderson Lizardo
2012-07-23 15:55 ` [RFC BlueZ 6/7] attrib-api: Add RegisterWatcher/UnregisterWatcher methods Anderson Lizardo
2012-07-23 15:55 ` [RFC BlueZ 7/7] doc: Add Register/Unregister GATT based services Anderson Lizardo
2012-07-24 9:27 ` Johan Hedberg [this message]
2012-07-24 9:53 ` [RFC BlueZ 0/7] Generic GATT API changes Johan Hedberg
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=20120724092702.GA8706@x220.ice.intel.com \
--to=johan.hedberg@gmail.com \
--cc=anderson.lizardo@openbossa.org \
--cc=claudio.takahasi@openbossa.org \
--cc=linux-bluetooth@vger.kernel.org \
/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).