Re: [ovirt-devel] Thoughts on modularization
----- Original Message -----
From: "Yair Zaslavsky" <yzaslavs(a)redhat.com>
To: "Alon Bar-Lev" <alonbl(a)redhat.com>
Cc: "Vojtech Szocs" <vszocs(a)redhat.com>, "Mark Proctor"
<mdproctor(a)gmail.com>, devel(a)ovirt.org
Sent: Wednesday, November 5, 2014 10:40:05 PM
Subject: Re: [ovirt-devel] Thoughts on modularization
>
> 4. there must be core model to trigger the entire thing, core cannot be
> just
> a loader.
Alon, can you elaborate here on number 4?
In an ideal world, wouldn't you want to have the "engine core" be a small
as
something that goes over the extensions and loads them? and maybe let each
extension expose somehow its relevant part of rest-api (besides of using
ext-api to interact between extension and of course each extension should
have the relevant logic implementerd within)
Well, there is a balance between generic and specific.
If you go this route, can the Java JRE be the core you are looking for?
The wisdom is to draw the line where the building blocks serves the purpose of building
the application you need.
Alon