- From: Julien Racle via GitHub <sysbot+gh@w3.org>
- Date: Thu, 28 Jul 2016 08:33:59 +0000
- To: public-web-bluetooth-log@w3.org
> I like having the per-realm boolean (spelled device.gatt.connected today) **saying whether that realm is holding the physical GATT connection open** Indeed that's a good description for `device.gatt.connected`, Realm holding physical connection, I get it now. > because **that lets the UA GC the physical connection when no more realms are holding it open**, even if some realms still have a reference to the BluetoothDevice object. Just one warning here, in case system still requires physical connection, UA should leave it open ( see [crbug.com/630586](http://crbug.com/630586) ). > I think that's not quite correct: a physical disconnection causes a logical disconnection, and the logical disconnection causes the gattserverdisconnected event. For the reverse, a physical connection wouldn't intrinsically cause a logical connection, so we'd want just a gattserverphysicallyconnected event. Agree! And also `gattserverphysicallyconnected` is probably not be relevant as of now as well. -- GitHub Notification of comment by jracle Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/256#issuecomment-235833522 using your GitHub account
Received on Thursday, 28 July 2016 08:34:08 UTC