W3C home > Mailing lists > Public > public-web-bluetooth-log@w3.org > December 2016

[web-bluetooth] BluetoothRemoteGATTServer.disconnect could return a promise

From: Gordon Williams via GitHub <sysbot+gh@w3.org>
Date: Mon, 19 Dec 2016 12:00:12 +0000
To: public-web-bluetooth-log@w3.org
Message-ID: <issues.opened-196397142-1482148809-sysbot+gh@w3.org>
gfwilliams has just created a new issue for 
https://github.com/WebBluetoothCG/web-bluetooth:

== BluetoothRemoteGATTServer.disconnect could return a promise ==
Hi,

Not sure if this is the right place, but please can I request a minor 
tweak to the Web Bluetooth spec? To make 
[`BluetoothRemoteGATTServer.disconnect`](https://webbluetoothcg.github.io/web-bluetooth/#bluetoothremotegattserver)
 return a promise (it should break anything).

At least on some platforms, disconnection seems to take a certain 
amount of time, and there are limits to the amount of active BLE 
connections.

I can totally imagine a situation where someone is trying to work 
their way around several Bluetooth devices that they have previously 
requested access to, and they're disconnecting from one device and 
connecting to another - but they'd be forced to add an arbitrary 
timeout so as not to go past the hardware/OS's connection limit.

This is exactly the issue I'm having with 
[puck.js](http://www.puck-js.com/) right now - I'm trying to implement
 a web bluetooth compliant API on the hardware, but as it is currently
 there can only be *one* outgoing connection. Users are having to 
manually add a ~200ms timeout to ensure that they can connect to a new
 device after calling disconnect.

thanks!

Please view or discuss this issue at 
https://github.com/WebBluetoothCG/web-bluetooth/issues/342 using your 
GitHub account
Received on Monday, 19 December 2016 12:00:18 UTC

This archive was generated by hypermail 2.3.1 : Monday, 19 December 2016 12:00:19 UTC