Re: [web-bluetooth] Clarify the role of requestDevice vs requestLEScan

My goal is to have folks who want to connect to a particular device, 
use `requestDevice()`, and folks who want a stream of advertisements 
from a bunch of nearby devices, use `requestLEScan()`. The devices 
returned by `requestLEScan()` should have a way to upgrade to GATT 
communication, but doing it that way will involve two permission 
requests (1 for scanning and 1 for the upgrade), while 
`requestDevice()` will only involve one request.

I don't want to limit `requestDevice()` to already-connected 
peripherals because that'll force users to find their OS-specific way 
to connect the device before pairing it to the website. We should let 
them do that in one step.

I'm happy to add text to the spec clarifying this; let me know what 
sort of text would help you the most.

-- 
GitHub Notification of comment by jyasskin
Please view or discuss this issue at 
https://github.com/WebBluetoothCG/web-bluetooth/issues/255#issuecomment-235741531
 using your GitHub account

Received on Wednesday, 27 July 2016 22:30:10 UTC