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

Re: [web-bluetooth] Treat sites as not bonded to their devices.

From: Jeffrey Yasskin via GitHub <sysbot+gh@w3.org>
Date: Tue, 23 Aug 2016 16:13:25 +0000
To: public-web-bluetooth-log@w3.org
Message-ID: <issue_comment.created-241787476-1471968803-sysbot+gh@w3.org>
@Vudentz In Bluetooth, if a device isn't bonded, when it disconnects 
the attribute cache also needs to be flushed, according to 3.G.2.5.2:

> For clients that have a trusted relationship (i.e. bond) with the 
server, the attribute cache is valid across connections. For clients 
with a trusted relationship and not in a connection when a service 
change occurs, the server shall send an indication when the client 
reconnects to the server. For clients that do not have a trusted 
relationship with the server, the attribute cache is valid only during
 the connection. 

So I think the terminology here is exactly in line with Bluetooth.

Yes, I called out the risk of missing notifications in 

If sites X, Y, and Z are connected, and X disconnects, X's attributes 
will get invalidated even though the platform is still connected and 
could avoid invalidating the attributes. That's the right thing to do 
so that developers don't have to/aren't tempted to write two different
 code paths for the two different cases.

GitHub Notification of comment by jyasskin
Please view or discuss this issue at 
 using your GitHub account
Received on Tuesday, 23 August 2016 16:13:33 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:58:23 UTC