[web-bluetooth] How to handle changing advertised UUIDs

• From: Giovanni Ortuno via GitHub <sysbot+gh@w3.org>
• Date: Thu, 08 Sep 2016 07:29:18 +0000
• To: public-web-bluetooth-log@w3.org
• Message-ID: <issues.opened-175683954-1473319756-sysbot+gh@w3.org>

g-ortuno has just created a new issue for 
https://github.com/WebBluetoothCG/web-bluetooth:

== How to handle changing advertised UUIDs ==
Step 8 of [get the BluetoothDevice 
representing](https://webbluetoothcg.github.io/web-bluetooth/#get-the-bluetoothdevice-representing)
  states:
> 8. Add device’s advertised Service UUIDs to 
result.[[unfilteredUuids]].

But it isn't clear what advertised Service UUIDs means when a device 
is alternating UUIDs. Is it only the last Advertised UUIDs? All the 
UUIDs we've seen during that particular scan or all the UUIDs we've 
seen so far across scans?

Given that only BlueZ caches the advertised UUIDs I think this should 
be specified.

Please view or discuss this issue at 
https://github.com/WebBluetoothCG/web-bluetooth/issues/290 using your 
GitHub account

Received on Thursday, 8 September 2016 07:29:25 UTC