Hey, Plain old UI Plugins can, in theory, use any backend they would like to. (I don't know MEAN, so not sure if this helps answer your question.) But the real power of oVirt.js is that it allows any type of JavaScript frontend to access ovirt-engine. Perhaps you want to write a super-light version of webadmin. You can do that with oVirt.js. Of course, Vojtech will have a way better answer than mine :) Greg ----- Original Message -----

Hi Yair, indeed, oVirt JS binding & oVirt.js library are meant to be used not only by our GWT-based UI (WebAdmin, UserPortal), but also by any 3rd party JS-based application/tool, be it a UI plugin, a totally custom UserPortal, or even Node.js-powered custom service talking with Engine. This is the reason for going with JavaScript-first approach, escaping the GWT/Java box and putting emphasis on JavaScript language/runtime. oVirt.js for JavaScript is meant to be what oVirt Java SDK is for Java, however oVirt.js should be usable from both client (i.e. browser) and server (i.e. Node.js) environment by providing reasonable abstractions. Some more comments below. Regards, Vojtech PS: the MEAN stack looks cool! ----- Original Message ----- +1 Generally speaking, UI plugin feature makes no assumptions of backend. But it's a (very) common requirement to integrate with oVirt Engine, so using oVirt.js within your UI plugin sounds like a common use case. You gave a very good answer, I have no comments :) Yes, we are aware of this. Before we go from PoC to stable, we will spend some time for discussing the final design (and possibly try to anticipate future changes that would reflect into API design/implementation).