- From: Vincent Scheib via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Apr 2020 01:27:18 +0000
- To: public-web-bluetooth-log@w3.org
This issue / patch to date has two outstanding areas I think need to be addressed before closing: a) We should address g-ortuno's [comment](https://github.com/WebBluetoothCG/web-bluetooth/pull/433/files#r277496051) which requests writeValue() be specified specifically e.g. "If the Write bit is set in characteristic’s properties, use the Write Characteristic Value procedure, otherwise use the Write without Response procedure." b) Perhaps Web Bluetooth should not be owning enforcing the algorithm selection based on Characteristic Properties. That is, if the application requests writeWithoutResponse we should attempt it by sending the request to the operating system without verifying Characteristic Properties. This question was raised by @dlech after discussing with @Vudentz on bluez patch thread [src/gatt-client: always check properties in WriteValue](https://marc.info/?t=158799982800006&r=1&w=2). Apparently some devices may operate with an algorithm even though they don't mark those property bits. -- GitHub Notification of comment by scheib Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/238#issuecomment-620939561 using your GitHub account
Received on Wednesday, 29 April 2020 01:27:19 UTC