W3C home > Mailing lists > Public > public-web-bluetooth-log@w3.org > August 2016

Re: [web-bluetooth] Don't fire characteristicvaluechanged for Read Responses

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
Message-ID: <issue_comment.created-240133667-1471360414-sysbot+gh@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. 

> 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 
 using your GitHub account
Received on Tuesday, 16 August 2016 15:13:43 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:58:23 UTC