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 > --- > Brian A. Redding > Employee of Qualcomm Innovation Center, Inc. > Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum 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! 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? Included services are not supported by our client. How important is it? It is mandatory for qualification? Regards, 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
