W3C home > Mailing lists > Public > public-script-coord@w3.org > July to September 2015

Web Bluetooth hybrid API

From: Rob Moran <Rob.Moran@arm.com>
Date: Thu, 24 Sep 2015 09:56:32 +0000
To: "public-script-coord@w3.org" <public-script-coord@w3.org>
Message-ID: <AM2PR08MB0180A78536C108E2FD336FB2E5430@AM2PR08MB0180.eurprd08.prod.outlook.com>
Hi group,

we've been following the web-bluetooth specification closely with interest and with a view to implementing it as an abstraction interface over other popular JavaScript-BLE implementations on web, server and mobile.

We are aware this is a web-bluetooth specification rather than JavaScript-bluetooth, however it does rely heavily on the use of ES6 promises, a paradigm not commonly used on many platforms (yet!).

Promises are an elegant approach to asynchronous programming, but even in web development the use of promises could perhaps be considered a choice of the developer and not forced by the API.

We were wondering if a hybrid approach was considered when defining the specification which allows the choice of using promises (if available) or a callback with an error object.

Examples of this approach can be seen in these npm modules:

https://www.npmjs.com/package/hybridify
https://www.npmjs.com/package/handle-callback

Forgive my ignorance if discussions around this are already public.


Kind regards,

Rob

________________________________

-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Received on Thursday, 24 September 2015 10:03:54 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 24 September 2015 10:03:55 UTC