| [concierge-dev] JavaScript and osgi |
Hi Guys,
I am a developer located in Zurich CH. I am currently writing an _javascript_ based OSGI container which is base around the Concierge project form ETH http://concierge.sourceforge.net/properties.html. My main reason for porting osgi to js is for the same reason osgi was created for java.
My main goals are/were
- Port only the required layers: modual, lifecycle, service, namespace, start level and framework, weaving
- Not all api method make sense in a js. No need to adapt classes
The main issues I can across were /are browser related:
- js code must run in async in browsers in order to not block the ui (single thread model). This required adapting some of the api to be async promise based (e.g., init, install, start …)
- there is no js classloader concept but there are modual loaders (require, amd, es6) how to best utilize them. I don’t really want to write my own loader or port the java classloader concept.
- File access and permissions are not available in browser but are on node.js. How to split the functionality up?
My work is in a private repo if you're interested to have a look? I should have an R3 compliant container ready by end of April. I believe osgi would work very well in browsers and on the server (node, vertx) and embedded (raspberry pi, etc). I would be in very interested in how you plan to proceed with Concierge. I think there is a need for an osgi microcontainer in java and in _javascript_.
In an effort to setup Concierge I created a maven build at:
https://github.com/jbadeau/Concierge.git
Feel free to copy it. If you do so then let me know and ill delete it and ref yours.
Cheers,
Jose Badeau