On 12/15/2016 03:57 AM, Benjamin Francis wrote:
Reasons for using Node for WoT APIs:
- NodeJS is now a very popular language for server side web development
and has a huge existing community and collection of modules to draw from.
Using NodeJS will help attract community contribution from web developers
who can easily add their own modules when hacking on the project.
What kind of module are you talking about here? Are they different from
the adapters written in Rust? In Foxbox, when you write an adapter, you
don't need to write a singe line of code to get it exposed as a Rest
API. It's all taken care of by the taxonomy router
(https://github.com/fxbox/foxbox/blob/master/src/taxonomy_router.rs)
based on what is exposed by the adapter. Adapters implement a well
defined interface, and we derive the Rest part from that. This is
limiting risks of heterogeneous APIs, and provides a clear separation of
concerns. For instance, the rules engine also rely on the same internal
interfaces, without needing to go through the Rest API.
- By comparison Rust is still relatively immature as a language for web
development as you can read about here <http://www.arewewebyet.org/>.
It's likely that our platform will need to interact with a large range of
existing software and services, especially once third parties start to use
it for their own projects. Rust may hold us back here while we wait for it
to mature.
Not sure which kind of service interactions you're talking about here.
Can you elaborate or provide examples?
- SensorWeb already started implementing the SensorThings API in NodeJS.
I'd suggest we will eventually want to share code between the cloud and
gateway WoT API <https://moziot.github.io/wot/> implementations.
I would be quite surprised if we were to reuse this SensorThings
implementation in a gateway. But happy to hear that you consider
SensorThings to be WoT compliant ;)
Fabrice
_______________________________________________
dev-platform mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-platform