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

Though I agree that differentiating between Read responses and 
Notifications would be nice, I feel we can't have a good enough 
implementation to guarantee that we will correctly mark the events. 
More specifically, in macOS there is no difference between Read and 
Notification. So we basically mark a value changed event as 'read 
response' if there is a pending read request. You could imagine a 
scenario where a read request is dispatched and a notification 
immediately arrives. In this case the event would be mark as a read 
response even though it is in fact a notification.

GitHub Notification of comment by g-ortuno
Please view or discuss this issue at
 using your GitHub account

Received on Friday, 3 February 2017 22:58:16 UTC