- From: Julien Racle via GitHub <sysbot+gh@w3.org>
- Date: Tue, 26 Jul 2016 16:04:58 +0000
- To: public-web-bluetooth-log@w3.org
jracle has just created a new issue for https://github.com/WebBluetoothCG/web-bluetooth: == Clarify GATT connection status / behavior == Following my reaction to #169 , I'd like to be clear about GATT connection state. For now it seems that [gatt.connected](https://webbluetoothcg.github.io/web-bluetooth/#dom-bluetoothremotegattserver-connected) reflects the state of an instance of `BluetoothRemoteGATTServer` being connected to an instance of `BluetoothDevice` (pure software matters). If we consider underlying connection from central to peripheral, we might already be connected to the peripheral (device) in question : why not having `device.gatt.connected === true` in that case? Other concern is the ability to [disconnect GATT server](https://webbluetoothcg.github.io/web-bluetooth/#dom-bluetoothremotegattserver-disconnect). I get the use cases, but maybe its wiser for a start to remove this feature, and leave underlying UA to garbage-collect connection(s) on script exit. That would also permit not closing connections if they are needed by the OS. Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/256 using your GitHub account
Received on Tuesday, 26 July 2016 16:05:07 UTC