- From: Martin Woolley via GitHub <sysbot+gh@w3.org>
- Date: Mon, 24 Dec 2018 08:35:09 +0000
- To: public-web-bluetooth-log@w3.org
I'm wondering if this is this ever going to be addressed? It's clearly a mistake in the Web Bluetooth specification. Characteristics may support both WRITE (requests) and WRITE WITHOUT RESPONSE and a browser cannot be expected to second guess which is the most appropriate to use for a given application. Only the application developer can decide whether reliability or responsiveness are their priorities. There need to be two distinct APIs available or a flag which allows developers to indicate which variant should be used. You can continue to default to the current auto (not very) magic approach for backward compatibility. There are plenty of examples of characteristics with both write operations supported, clearly documented at bluetooth.com. -- GitHub Notification of comment by bluetooth-mdw Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/238#issuecomment-449702985 using your GitHub account
Received on Monday, 24 December 2018 08:35:10 UTC