- From: Michael Dietz via GitHub <sysbot+gh@w3.org>
- Date: Tue, 01 Mar 2016 14:59:43 +0000
- To: public-web-bluetooth-log@w3.org
I think this is necessary as well. I have a use case for this where we are doing a firmware transfer over the air, the link is lost for some reason, and the first thing we need to do is re enable notifications on a characteristic before starting the transfer where we left off. Whether we always write the descriptor no matter what, or we actually read it and only write it if it is not enabled is up to you (i can't think of any problems with either way but the second seems a bit cleaner). -- GitHub Notification of comment by mjdietzx Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/220#issuecomment-190756865 using your GitHub account
Received on Tuesday, 1 March 2016 14:59:45 UTC