Re: [web-bluetooth] Missing API for GATT Write w/o Response (#238)

I don't think we should abstract the Web Bluetooth developer too far from
the Bluetooth specification. When you write an app, you should know which
properties are supported for each individual GATT characteristic that you
are interacting with. It is very easy to figure this out in the chrome
browser if you do not have access to documentation (
chrome://bluetooth-internals/#devices  ).

There should be 2 write methods (write w/o response and write w/ response)
in addition to the existing "best effort write" which should remain for
backward compatibility.

My two cents...

On Tue, Apr 28, 2020 at 6:34 PM Vincent Scheib <notifications@github.com>
wrote:

> My personal thoughts on:
>
> a) writeValue should be specified to follow a specific algorithm. I agree
> with @g-ortuno <https://github.com/g-ortuno>'s preferring
> writeWithResponse.
>
> b) I believe Web Bluetooth should not check characteristic properties.
> Applications can access characteristic properties to check themselves if
> needed. If an algorithm can work with a device advertising incorrect
> property bits I'd like the application to have a chance to attempt it.
>
> If the algorithm won't work it will fail regardless. The value of having
> Web Bluetooth check would be i) consistent error type and ii) cross
> platform consistency. But these come at the expense of application
> functionality.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/WebBluetoothCG/web-bluetooth/issues/238#issuecomment-620941420>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ACNNFKNREUSXZFOTTR2SERTRO57ZLANCNFSM4CC422ZQ>
> .
>


-- 
GitHub Notification of comment by MikeTheDane
Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/238#issuecomment-620961502 using your GitHub account

Received on Wednesday, 29 April 2020 02:44:37 UTC