----- Original Message -----
From: "Yair Zaslavsky" <yzaslavs@redhat.com> To: "Sven Kieske" <s.kieske@mittwald.de> Cc: devel@ovirt.org Sent: Wednesday, November 5, 2014 9:34:20 PM Subject: Re: [ovirt-devel] Thoughts on modularization
----- Original Message -----
From: "Sven Kieske" <s.kieske@mittwald.de> To: devel@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
Exactly :)
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@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel