Re: [web-bluetooth] Should connectGATT() time out or wait until a device is available?

https://bugs.chromium.org/p/chromium/issues/detail?id=620405#c6 
mentions that there's a way to get BlueZ to do a hanging connect. We 
should change the code to use that if possible.

On Android, there's also a way to do a hanging connect 
([BluetoothGatt.connect()](https://developer.android.com/reference/android/bluetooth/BluetoothGatt.html#connect())
 or [BluetoothDevice.connectGatt(..., true, 
...)](https://developer.android.com/reference/android/bluetooth/BluetoothDevice.html#connectGatt(android.content.Context,
 boolean, android.bluetooth.BluetoothGattCallback))), but they may not
 work until we've connected once to the device with the timeout. We 
should experiment to see what's possible and then make the spec match.

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

Received on Thursday, 15 September 2016 17:27:57 UTC