Hi Claudio, -----Original Message----- From: Claudio Takahasi [mailto:claudio.takahasi@xxxxxxxxxxxxx] Sent: Monday, October 31, 2011 4:11 PM To: Tsai, Mike Cc: linux-bluetooth@xxxxxxxxxxxxxxx Subject: Multiple instances of same characteristics (was: Re: GATT Dbus API on BlueZ - attirbute-api.txt modifications) Hi Mike, > [MT]How can this handle the multiple instances of same characteristics within a single service? The characteristic UUID will not be unique in that case. Also, how is the profile specific characteristic descriptor handled? > > Cheers, > > Mike I am moving your question to another thread. The original thread is almost impossible to follow. Do you mean support for client characteristic configuration and other characteristics per device? In the Generic Attribute API(client), the represented characteristics are always per device. The abstraction for per device characteristic value needs to implemented in the server. The current attribute server supports CCC only, before implementing per device characteristics we need to cleanup the code. [MT]Yes, I think blueZ can handle the multiple devices with same service based on its inherent device architecture. The question was regarding the same characteristics within a single service in a single device. Based on Anderson's answer, I think the problem is also resolved. The profile specific descriptors (in automation and in HID services) will need to be addressed later, BR, Mike BR, Claudio. ��.n��������+%������w��{.n�����{��� �^n�r������&��z�ޗ�zf���h���~����������_��+v���)ߣ�
