[ovirt-devel] Thoughts on modularization

Yair Zaslavsky yzaslavs at redhat.com
Wed Nov 5 20:34:20 UTC 2014



----- Original Message -----
> From: "Sven Kieske" <s.kieske at mittwald.de>
> To: devel at ovirt.org
> Sent: Wednesday, November 5, 2014 6:36:39 PM
> Subject: Re: [ovirt-devel] Thoughts on modularization
> 
> 
> 
> On 05/11/14 17:07, Vojtech Szocs wrote:
> > This way, you'd have one "core" module, providing most general
> > functionality/abstractions. Then you'd have more specific modules,
> > plugged into "core" module's API etc. In other words, hierarchy of
> > modules. This is essentially modularization taken to extreme :)
> 
> Welcome to dependency hell or circular dependencies etc.
> 
> would you like to code your own dependency resolver?

I assume dependency resolving can be based on Topological sorting of Graph theory.
I assume the extensions that will participate as nodes in the graph will be those who are enabled in their configuration

> 
> I like modularization, but you can overengineer everything.
> 
> --
> Mit freundlichen Grüßen / Regards
> 
> Sven Kieske
> 
> Systemadministrator
> Mittwald CM Service GmbH & Co. KG
> Königsberger Straße 6
> 32339 Espelkamp
> T: +49-5772-293-100
> F: +49-5772-293-333
> https://www.mittwald.de
> Geschäftsführer: Robert Meyer
> St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
> Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
> _______________________________________________
> Devel mailing list
> Devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel



More information about the Devel mailing list