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

Re: [web-bluetooth] Specify a Bluetooth Scanning API.

From: Jeffrey Yasskin via GitHub <sysbot+gh@w3.org>
Date: Wed, 25 May 2016 15:40:51 +0000
To: public-web-bluetooth-log@w3.org
Message-ID: <issue_comment.created-221616466-1464190849-sysbot+gh@w3.org>
I think we don't need to distinguish between ADV_IND and 
ADV_DIRECT_IND: the difference is whether the controller can send a 
SCAN_REQ in response, but the advertising event should just combine 
data from the advertisement with the SCAN_RSP, so websites don't need 
to react to the difference.

Do we want to mark this in the advertising event or on the device? I'd
 initially thought the advertising event, but since we always have to 
wait for a subsequent advertisement in order to connect, it probably 
makes sense to turn it to 'true' on the device as soon as we see any 
connectable advertisement from that device.

-- 
GitHub Notification of comment by jyasskin
Please view or discuss this issue at 
https://github.com/WebBluetoothCG/web-bluetooth/pull/239#issuecomment-221616466
 using your GitHub account
Received on Wednesday, 25 May 2016 15:40:54 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 25 May 2016 15:40:54 UTC