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

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

From: Jeffrey Yasskin via GitHub <sysbot+gh@w3.org>
Date: Wed, 17 Aug 2016 13:14:57 +0000
To: public-web-bluetooth-log@w3.org
Message-ID: <issue_comment.created-240406878-1471439695-sysbot+gh@w3.org>
I would also prefer @beaufortfrancois' first option if we make a 

@Emill, what's your use case for distinguishing reads from 
notifications in the `characteristicvaluechanged` event? I want to try
 to avoid changing things based on just "might be important", but it 
seems like you probably actually ran into this when trying to do 
something concrete, so I'd like to explore what the concrete thing is.

Guessing, it seems like to run into this you'd need to be using the 
same characteristic for two different purposes, perhaps returning 
unrelated values from a read vs a notification. If I've got that 
right, why is that the right design instead of using two different 

GitHub Notification of comment by jyasskin
Please view or discuss this issue at 
 using your GitHub account
Received on Wednesday, 17 August 2016 13:15:03 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 17 August 2016 13:15:04 UTC