Hi Luiz, Earlier I chatted with Marcel on IRC about how we can resolve the notification subscription issue that you were concerned about (basically a server connecting and immediately sending a notification). I think our consensus was that this mainly applies when the two devices are bonded. In that case, we could make it so that the exported GattService1 hierarchy stays around over disconnections if there is a bond between the two devices. We would keep StartNotify/StopNotify and keep around the data on external clients that subscribed to notifications. Upon reconnection we would then immediately register for notifications based on all the external clients that subscribed. Would this address the case? I think this case really applies when the remote CCC has been configured so the peripheral remembers the configuration between disconnections, which should only happen when the devices are bonded but I'm not sure. Let me know if that makes sense! Thanks! Arman -- 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
