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

- Linux Kernel < 3.15 has a 40s timeout
- Linux Kernel >= 3.15 has a 20s timeout
- Android timeout is 30s
- Mac doesn't have a timeout

I wonder if we should internally call `disconnect()` after a certain 
amount of time to consistency across platforms. If I'm developing on 
Android, I might not implement the timeout after x seconds because 
`device.gatt.connect` would fail after 30s which I'm fine with. 
However, on Mac, it won't and this will leave my application in a 
weird state.

I suggest we always call disconnect after 20s to be consistent.

@jyasskin WDYT?

Please close if it doesn't make sense.

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

Received on Wednesday, 14 September 2016 08:30:12 UTC