From: Anderson Lizardo <anderson.lizardo@openbossa.org>
To: linux-bluetooth@vger.kernel.org
Cc: Anderson Lizardo <anderson.lizardo@openbossa.org>
Subject: [RFC BlueZ 3/7] attrib-api: Remove GATT service hierarchy
Date: Mon, 23 Jul 2012 11:55:16 -0400 [thread overview]
Message-ID: <1343058920-18608-4-git-send-email-anderson.lizardo@openbossa.org> (raw)
In-Reply-To: <1343058920-18608-1-git-send-email-anderson.lizardo@openbossa.org>
---
doc/attribute-api.txt | 54 -------------------------------------------------
1 file changed, 54 deletions(-)
diff --git a/doc/attribute-api.txt b/doc/attribute-api.txt
index 6560b53..4c29f66 100644
--- a/doc/attribute-api.txt
+++ b/doc/attribute-api.txt
@@ -12,60 +12,6 @@ service that contains it, so clients can identify the correct characteristic if
multiple services contain the same characteristic.
-Device Service hierarchy
-========================
-
-Service org.bluez
-Interface org.bluez.Characteristic
-Object path [prefix]/{hci0}/{device0}/{service0, service1, ...}
- [prefix]/{hci0}/{device1}/{service0, service1, ...}
-
-Methods dict GetProperties()
-
- Returns all properties for the interface. See the
- Properties section for the available properties.
-
- array{object} DiscoverCharacteristics()
-
- Discover all characteristics that belongs in this service.
- When it returns all the characteristics paths will be
- already registered. It will return the characteristics paths
- as soon as they are discovered. After that it will try to
- read all values.
-
- RegisterCharacteristicsWatcher(object agent)
-
- Register a watcher to monitor characteristic changes.
-
- A watcher will be registered for this service and will
- notify about any changed characteristics in the service.
- This also notifies about any included characteristics.
-
- UnregisterCharacteristicsWatcher(object agent)
-
- Unregister a watcher.
-
-Properties string Name (mandatory) [readonly]
-
- General name of service
-
- string Description (optional) [readonly]
-
- Description of service
-
- string UUID (mandatory) [readonly]
-
- UUID of service. Service class value for SDP and GATT
- UUID for attribute based services.
-
- array{object} Characteristics [readonly]
-
- This list contains the characteristics owned by this
- specific service and other characteristics from service
- includes. That way no complicated service includes array
- is needed.
-
-
Device Characteristic hierarchy
===============================
--
1.7.9.5
next prev parent reply other threads:[~2012-07-23 15:55 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 ` Anderson Lizardo [this message]
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
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=1343058920-18608-4-git-send-email-anderson.lizardo@openbossa.org \
--to=anderson.lizardo@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).