- From: Giovanni Ortuno via GitHub <sysbot+gh@w3.org>
- Date: Tue, 16 Aug 2016 15:13:36 +0000
- To: public-web-bluetooth-log@w3.org
> Also, now as far as I can see, it's impossible to distinguish a characteristicvaluechanged that happened due to a read from one that happend due to a notification, which might be important when you want to implement something on top of GATT. I don't think we would be able to implement this given that macOS follows pretty much the same pattern. https://developer.apple.com/reference/corebluetooth/cbperipheraldelegate/1518708-peripheral?language=objc > The term "characteristic value changed" also does not apply really to the read procedure; the value hasn't changed, you just got a copy of what's stored in the peripheral. For notifications however, the value has usually changed when a notification is sent. I don't think this was meant to imply that the actual value has changed but rather that we *updated* our copy of the value. Maybe `characteristicvalueupdated` would be more appropriate. -- GitHub Notification of comment by g-ortuno Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/274#issuecomment-240133667 using your GitHub account
Received on Tuesday, 16 August 2016 15:13:43 UTC