Hi Claudio, On Wed, Oct 06, 2010, Claudio Takahasi wrote: > Initial implementation of per client attribute configuration for the > attribute server. Notification and indication shall be sent to the peer > only if Client Characteristic Configuration bit field is set. > --- > TODO | 7 -- > src/attrib-server.c | 194 +++++++++++++++++++++++++++++++++++--------------- > src/storage.c | 44 ++++++++++++ > src/storage.h | 4 + > 4 files changed, 184 insertions(+), 65 deletions(-) I feel a bit conflicted about this one. Do we really want to have a generic storage for all characteristics? I'd think that it'd make sense to let each service implementation take care of how to store their state persistently (if it needs to be done at all). Would it be possible for you to create a patch that fixes the notification sending to clients that haven't subscribed for them but leaves out the storage stuff? Johan -- 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
