- From: Jeffrey Yasskin <jyasskin@google.com>
- Date: Fri, 7 Aug 2015 11:01:25 -0700
- To: François Beaufort 🇫🇷 <fbeaufort@google.com>
- Cc: public-web-bluetooth <public-web-bluetooth@w3.org>
Yep, that looks about right. Like I replied in the getDevices document, I'm not sure we want UAs to be in charge of sorting the devices list by recency of use, but web pages can certainly use that as their reconnection order. On Fri, Aug 7, 2015 at 3:48 AM, François Beaufort 🇫🇷 <fbeaufort@google.com> wrote: > Thank you Jeffrey for sharing these sketches. > > I'd like to share also some code I wrote which helps me to get the full > picture: http://pastebin.com/dTrM48G8 > This code features one way of doing Physical Web detection and handling > session resuming. > It is not necessarily "the" way to go but it gives a sense of what we're > trying to accomplish here. > > Let me know if that makes sense. > > On Thu, Aug 6, 2015 at 10:28 PM Jeffrey Yasskin <jyasskin@google.com> wrote: >> >> Hi Web Bluetooth CG, >> >> A couple folks have asked how Web Bluetooth will interact with >> Eddystone and how websites can handle reloads without showing another >> dialog. I have sketches of possible designs for this at >> >> https://docs.google.com/document/d/1jFCTyq84T2fLc8ZhxorTz3u_gCk59hp17EmkFgaDQ2c/edit?usp=sharing >> (Eddystone) and >> >> https://docs.google.com/document/d/1QLEi4lK4St3tS_EQEKqhTOn5Gi47sN5mUoLCm4tOyr8/edit?usp=sharing >> (getPairedDevices). I'm not sure the new interfaces will be in the >> first version of the Web Bluetooth spec or implementation, since I'd >> like to constrain that to the smallest interface that works for >> people, but if there's a lot of interest and agreement on the shape we >> want, I can pull them into the spec. >> >> Please look these over and let me know what you think, either with >> replies to this email or comments on the documents. >> >> Thanks, >> Jeffrey >> >
Received on Friday, 7 August 2015 18:02:14 UTC