- From: Jeffrey Yasskin via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 Jan 2016 19:19:03 +0000
- To: public-web-bluetooth-log@w3.org
We're not planning to expose the raw bytes, but custom formats, including Eddystone and iBeacon, use the standard [manufacturer](https://webbluetoothcg.github.io/web-bluetooth/#dom-bluetoothadvertisingdata-manufacturerdata) or [service data](https://webbluetoothcg.github.io/web-bluetooth/#dom-bluetoothadvertisingdata-servicedata) fields, which we do expose. There's even an [example of parsing Apple's format](https://webbluetoothcg.github.io/web-bluetooth/#example-145d3a9c). These aren't implemented anywhere yet, and they're not going to be as useful as they should be until we add a scanning API (to find all nearby beacons), which isn't coming until the next version of the API (after GATT communication ships). -- GitHub Notification of comment by jyasskin Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/204#issuecomment-175807029 using your GitHub account
Received on Wednesday, 27 January 2016 19:19:05 UTC