Ticket #2475 (new enhancement)
|Reported by:||pulponair||Owned by:|
|Priority:||minor||Milestone:||ispCP ω 1.2.0|
|Component:||Backend (Engine)||Version:||ispCP ω 1.0.6|
ATM the domain manager consists of a lot of subroutines that are called sequently on domain addition/deletion etc.
In order to make things more flexible and modular i would suggest to add some sort of "module registration" mechanism. So the domain manager would do nothing but calling module methods (and passing over parameters) registered for a certain "event" e.g. domain addition.
The actuall code should reside within the module. Module registration could happen within a global configuration file or similar.
To enable a certain excution order there should be the possibillty to pass a priority value at registration.
Module specific settings could be registered by the module itself and passed over to it at execution.
Module specific configuration templates should reside within the module itsefl as well.
Furthermore it would be greate to have something like a local folder to override the templates shipped with the module.
Moving over to the module concept would highly ease user contribute. E.g. someone could provide a general "external module" that allows people to contribute modules written in languages other than perl..