HI François, On Mon, Jul 18, 2016 at 11:52 AM, François Beaufort <beaufort.francois@xxxxxxxxx> wrote: > For info, we'll track check for CCC descriptors at > https://bugs.chromium.org/p/chromium/issues/detail?id=624763 Up to you, but we may as well just disallow that over D-Bus if we don't have a reason to keep this policy, but then again this is a reflection of stacks that don't manage notification themselves so there is always a risk the application will not get these details quite right breaking the notifications, if I were to enforce this I would probably file an errata to the spec outlining the requirements to support notification which may or may not end up allowing unsolicited notifications/indications. Note that unsolicited notifications may not be a bad idea since the implementation of CCC is quite expensive given that it needs to be persisted, also for services provided by application it may not be possible to restore the CCC because the database may have changed. Luiz Augusto von Dentz -- 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
