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

Yes, CoreBluetooth is not so good in this case. But both solutions 
handles this wrong, i.e. you can get a read request's promise resolved
 with a notified value rather than the correct read response. We've 
actually sent a bug report to Apple telling them that it's impossible 
to distinguish between a read response and a notification.

By the way, noble uses a lower level mechanism in Mac OS X to really 
solve this problem:
 It seems there is actually an isNotification parameter that is 
removed by the outer API.

GitHub Notification of comment by Emill
Please view or discuss this issue at
 using your GitHub account

Received on Friday, 3 February 2017 23:37:56 UTC