> -----Original Message----- > From: Claudio Takahasi [mailto:claudio.takahasi@xxxxxxxxxxxxx] > Sent: Monday, October 25, 2010 9:52 PM > > Hi Brian, > > On Mon, Oct 25, 2010 at 4:27 PM, Brian Redding > <bredding@xxxxxxxxxxxxxx> wrote: > > Hi Claudio, > > > > Are there still interfaces that need to be added to attribute-api.txt > > to handle client and server characteristic configuration as well as > > presentation and aggregate formats? I see those as TODO items but > > wondered if the APIs for them have been defined yet. > > > > One thing to note on the server API is that a GATT-based profile > > could specify behavior on a characteristic value that when the > > characteristic value is read to perform some action in a similar way as > > a hardware register. It appears that the notes I'm reading in the code > > thus far only consider changes (or writes) to characteristic values for > > the watch code. > > > > Also does the current API handle included services? > > > > The Bluetooth SIG is beginning to look at 3rd party application > > developer API's for both client and servers for various platforms so > > understanding what is currently defined in BlueZ and what still needs > > to be added would be useful. > > > > Thanks, > > Brian > > The API to address characteristic descriptors is still being defined. > We are focusing in the advertising and connection management at the > moment. If you have suggestion of how to represent the descriptors in > the attribute API, suggestions are welcome! Once I feel more comfortable with the current API approach, I will see if I can suggest something. One thing to note is that GATT only list the current characteristic descriptors. Profiles can specify additional ones or a group of generic ones could also be adopted in the future. One example of this is a characteristic descriptor that defines triggers that cause a particular behavior to occur when a condition on the characteristic value occurs. > > There isn't a server API at the moment, we implemented a server for > testing purpose only. But we will need to define it soon. > Which pages/section of the spec describes this read characteristic > behavior? The GATT does not specify the read characteristic behavior but it can be specified by a profile. I just wanted to point that out so that the design takes that into account. You may need to have a call back when a characteristic value is read as well as written. > > Included services are not supported by our client. How important is > it? It is mandatory for qualification? It is only mandatory on the server. > > Regards, > Claudio. Cheers, Brian --- Brian A. Redding Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum -- 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
