Hi, This RFC series contain a proposal for a internal API that simplifies GATT service registration on server implementations. It is built on top of current "low level" attribute API, and both can be used at the same time without problem. As an example, I converted a service from the GATT example profile (see patch #3). I would like to hear your opinion on the approach (using varargs). There are some limitations on current implementation: * No support for aggregate format descriptors, included services * Support for many descriptors is missing * No support for "static" characteristic values. All readable or writeable * characteristic needs a corresponding read or write callback Comments are very welcome, even if it is to propose another API. Regards, -- Anderson Lizardo Instituto Nokia de Tecnologia (INdT) Manaus - Brazil -- 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
