- From: Jeffrey Yasskin via GitHub <sysbot+gh@w3.org>
- Date: Thu, 10 Mar 2016 19:09:31 +0000
- To: public-web-bluetooth-log@w3.org
There are some characteristics (Service Changed comes to mind, although it's not user-visible) that queue up information to send to bonded devices, and then dump it out on re-connection. If we make sites re-register for notifications/indications on re-connection, they'll generally miss that set of notifications. @Vudentz also makes that point at the bottom of http://permalink.gmane.org/gmane.linux.bluez.kernel/66966. That said, it's going to be a fair amount of bookkeeping in the UA to keep the queue of notifications that a site hasn't seen. Maybe we should make them re-retrieve the data. The spec definitely should say that non-bonded devices clear their notification set on disconnection. -- GitHub Notification of comment by jyasskin Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/220#issuecomment-195004482 using your GitHub account
Received on Thursday, 10 March 2016 19:09:34 UTC