- From: Jeffrey Yasskin <jyasskin@google.com>
- Date: Thu, 11 Aug 2016 17:27:16 -0700
- To: public-web-bluetooth <public-web-bluetooth@w3.org>
And https://github.com/WebBluetoothCG/web-bluetooth/pull/273 specifies
that you can't save attributes across disconnection, making websites
act as if they're not-bonded to their devices. Look at that one after
#272.
On Wed, Aug 10, 2016 at 4:58 PM, Jeffrey Yasskin <jyasskin@google.com> wrote:
> https://github.com/WebBluetoothCG/web-bluetooth/pull/272 specifies
> that when a ServiceChanged indication is received that says some
> attributes don't exist anymore, those attributes' objects get
> permanently disconnected from the device. If a later ServiceChanged
> indication arrives saying the attributes have re-appeared, they need
> to be re-discovered. Please let me know if you like the direction of
> the change (but read the issues below if you dislike it), and if I've
> made any mistakes in specifying it.
>
> This fixes https://github.com/WebBluetoothCG/web-bluetooth/issues/130
> ("Describe what to do if a method is called on a removed attribute"),
> and lays the groundwork to fix
> https://github.com/WebBluetoothCG/web-bluetooth/issues/226 ("Treat
> devices as if they weren't bonded to websites that have access to
> them."), which makes the right fix for
> https://github.com/WebBluetoothCG/web-bluetooth/issues/220
> ("startNotifications should always write descriptor if device is not
> bonded") clear.
>
> Thanks,
> Jeffrey
Received on Friday, 12 August 2016 00:28:07 UTC