Return-Path: MIME-Version: 1.0 In-Reply-To: References: <20120319230436.GA27304@x220> <20120320173546.GA6307@samus> <20120321124517.GB8888@x220> Date: Wed, 21 Mar 2012 10:18:35 -0400 Message-ID: Subject: Re: Query on attribute api service object path From: Anderson Lizardo To: Jaganath Cc: linux-bluetooth@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi, On Wed, Mar 21, 2012 at 9:11 AM, Jaganath 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). Regards, -- Anderson Lizardo Instituto Nokia de Tecnologia - INdT Manaus - Brazil