On Wed, Sep 29, 2010 at 10:49 AM, Johan Hedberg <johan.hedberg@xxxxxxxxx> wrote:
> Hi,
>
> On Tue, Sep 28, 2010, Claudio Takahasi wrote:
>> +Attribute Protocol hierarchy
>> +============================
>> +
>> +Service       Âorg.bluez
>> +Interface  Âorg.bluez.Attribute
>> +Object path Â[prefix]/{hci0}/{device0}
>> +
>> +
>> +Methods       Âdict GetProperties()
>> +
>> + Â Â Â Â Â Â Â Â Â Â Returns all properties for the interface. See the
>> + Â Â Â Â Â Â Â Â Â Â properties section for available properties.
>> +
>> +Properties  array{object} Services
>> +
>> + Â Â Â Â Â Â Â Â Â Â List of all the Primary Services that this device
>> + Â Â Â Â Â Â Â Â Â Â implements.
>> +
>> +
>> ÂDevice Service hierarchy
>> Â========================
>>
>> diff --git a/doc/device-api.txt b/doc/device-api.txt
>> index 95b5b22..b818299 100644
>> --- a/doc/device-api.txt
>> +++ b/doc/device-api.txt
>> @@ -139,10 +139,6 @@ Properties    string Address [readonly]
>> Â Â Â Â Â Â Â Â Â Â Â List of 128-bit UUIDs that represents the available
>> Â Â Â Â Â Â Â Â Â Â Â remote services.
>>
>> - Â Â Â Â Â Â array{object} Services [readonly]
>> -
>> - Â Â Â Â Â Â Â Â Â Â List of characteristics based services.
>> -
>> Â Â Â Â Â Â Â boolean Paired [readonly]
>>
>> Â Â Â Â Â Â Â Â Â Â Â Indicates if the remote device is paired.
>
> What's the motivation of moving this into its own D-Bus interface? I
> thought the plan was to abstract both traditional SDP and ATT behind the
> same API in which case having this in the Device interface makes more
> sense imho.
>
> Johan
>
Hi Johan,
we forgot the SDP integration plan. Forget this patch.
>From the implementation point of view, implement inside the attrib
client plugin was the easiest way, if we keep this property inside the
Device interface a new function needs to be created in device.h to
register the available primary services object paths.
Claudio.
--
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
