From: Anderson Lizardo <anderson.lizardo@openbossa.org>
To: linux-bluetooth@vger.kernel.org
Cc: Anderson Lizardo <anderson.lizardo@openbossa.org>
Subject: [PATCH RFC BlueZ v2 1/1] doc: Document Broadcaster/Observer API
Date: Thu, 26 Apr 2012 17:03:26 -0400 [thread overview]
Message-ID: <1335474206-21914-2-git-send-email-anderson.lizardo@openbossa.org> (raw)
In-Reply-To: <1335474206-21914-1-git-send-email-anderson.lizardo@openbossa.org>
---
doc/adapter-api.txt | 71 +++++++++++++++++++++++++++++++++++++++++++++++++++
1 files changed, 71 insertions(+), 0 deletions(-)
diff --git a/doc/adapter-api.txt b/doc/adapter-api.txt
index 0cded8c..346e7c3 100644
--- a/doc/adapter-api.txt
+++ b/doc/adapter-api.txt
@@ -181,6 +181,55 @@ Methods dict GetProperties()
Possible errors: org.bluez.Error.DoesNotExist
+ void RegisterBroadcaster(dict values)
+
+ Set Advertising data for broadcast. Different
+ applications can register different Adv. data types,
+ and they are all concatenated to form the Adv. data.
+ Broadcasting is enabled as soon as the first
+ RegisterBroadcaster() call is made.
+
+ Use UnregisterBroadcaster() to release Adv. data for
+ the application. Advertising data is also released when
+ application exits, and once the last Broadcaster exits,
+ advertising is disabled.
+
+ Possible Errors: org.bluez.Error.InvalidArguments
+ org.bluez.Error.Failed
+
+ void UpdateBroadcastData(dict values)
+
+ Replace Advertising data for broadcast. This method can
+ only be called after RegisterBroadcaster().
+
+ Possible errors: org.bluez.Error.Failed
+
+ void UnregisterBroadcaster()
+
+ This method will release any previously set Advertising
+ data.
+
+ Note that a broadcast procedure is shared between all
+ sessions, thus calling UnregisterBroadcaster() will
+ only release a single session.
+
+ Possible errors: org.bluez.Error.Failed
+
+ void RegisterObserver(object agent, array{byte} data_types)
+
+ Registers an observer agent to monitor broadcasts. This
+ agent will be notified whenever a broadcast is received
+ that contains any of selected Advertising data types.
+
+ Possible errors: org.bluez.Error.InvalidArguments
+
+ void UnregisterObserver(object agent)
+
+ Unregisters an observer. Broadcasts will not be
+ notified to this agent anymore.
+
+ Possible errors: org.bluez.Error.InvalidArguments
+
Signals PropertyChanged(string name, variant value)
This signal indicates a changed value of the given
@@ -276,6 +325,14 @@ Properties string Address [readonly]
Indicates that a device discovery procedure is active.
+ boolean Broadcasting [readonly]
+
+ Indicates that a broadcast procedure is active.
+
+ boolean Observing [readonly]
+
+ Indicates that an observation procedure is active.
+
array{object} Devices [readonly]
List of device object paths.
@@ -284,3 +341,17 @@ Properties string Address [readonly]
List of 128-bit UUIDs that represents the available
local services.
+
+
+Observer hierarchy
+==================
+
+Service unique name
+Interface org.bluez.Observer
+Object path freely definable
+
+Methods void BroadcastReceived(string address, byte data_type,
+ variant value)
+
+ This callback gets called when a broadcast data has
+ arrived with selected Advertising Data type.
--
1.7.5.4
prev parent reply other threads:[~2012-04-26 21:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 1:04 [RFC PATCH BlueZ] LE Broadcaster/Observer API proposal Anderson Lizardo
2012-04-12 1:04 ` [RFC PATCH BlueZ] doc: Document Broadcaster/Observer API Anderson Lizardo
2012-04-16 8:07 ` Ganir, Chen
2012-04-16 12:10 ` Anderson Lizardo
2012-04-17 5:42 ` Ganir, Chen
2012-04-16 8:03 ` [RFC PATCH BlueZ] LE Broadcaster/Observer API proposal Ganir, Chen
2012-04-16 11:52 ` Anderson Lizardo
2012-04-17 5:40 ` Ganir, Chen
2012-04-26 21:03 ` [PATCH RFC BlueZ v2 0/1] " Anderson Lizardo
2012-04-26 21:03 ` Anderson Lizardo [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=1335474206-21914-2-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).