- From: Per Thomas Jahr via GitHub <sysbot+gh@w3.org>
- Date: Mon, 21 Dec 2015 08:02:18 +0000
- To: public-web-bluetooth-log@w3.org
@g-ortuno I find the webbluetooth spec a bit unclear when it comes to disconnect. F.ex. should it be possible to call device.connectGATT() after a disconnect without calling requestDevice() first? Furthermore is states that " the UA MAY destroy device@[[representedDevice]]’s ATT Bearer" - is this the same as calling BluetoothGatt.java#close() or only BluetoothGatt.java#disconnect()? I found that only using disconnect will make the adapter stale after some time (at least on Nexus 5). Another unclear section: "If the UA is currently connected to this device’s GATT server, gattServer provides a way to interact with it. While this device is disconnected, gattServer is null." But if gattServer is null, developers can't use the readonly attribute "connected" of BluetoothGATTRemoteServer. -- GitHub Notification of comment by perja12 Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/192#issuecomment-166228144 using your GitHub account
Received on Monday, 21 December 2015 08:02:27 UTC