Hi Anderson,
--------------------------------------------------
From: "Anderson Lizardo" <anderson.lizardo@xxxxxxxxxxxxx>
Sent: Wednesday, March 21, 2012 7:48 PM
To: "Jaganath" <jaganath.k@xxxxxxxxxxx>
Cc: <linux-bluetooth@xxxxxxxxxxxxxxx>
Subject: Re: Query on attribute api service object path
Hi,
On Wed, Mar 21, 2012 at 9:11 AM, Jaganath <jaganath.k@xxxxxxxxxxx> wrote:
Hello,
I have a doubt in attribute-api.txt.
In Device service hierarchy object path is
"[prefix]/{hci0}/{device0}/{service0, service1, ...}.
which is device path + service"x".
When I checked the code "x" is "prim->start" which is service start
handle.
But how user will get this handle to create object path?
Only uuids are passed to user in UUIDs signal afaik.
Take a look on how to use the API on the test/test-attrib python
script. You should not try to parse the path itself. it is returned by
Methods and you simply use then with a D-Bus interface (e.g.
Bluez.Attribute).
Thanks for your reply. Characteristic based Service object path is there in
device properties.
Jaganath
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
