We are using the MVC app folder in all our sites through an SVN: External, and each site also has its files Settings files are specific to the site.
We require the system to have different functionality for each site. The main functionality should remain the same
Currently the options we consider are:
a: embedding feature condition in core
C: a controller file Turn on / off features on / off
b: Obtain override / existing controllers
c: Implement a modular system (plugins) with unlimited hooks within the core Make and Configure
Option B Already Exabled Has, however, to maintain long-term problems of difficulty, and it is quite hack.
Option B is already implemented, but it is difficult to maintain (as we have a new feature, we have to edit the files of each site, if it is overwritten
Option c is a solution that we have tried to fix recently and has thought of fixing it by editing a shared control plugin and a site-specific settings file. / P>
It is good to know If someone has any experience with any option that we have already thought, then if any other option knows which will be a better fit.
Option
Large scale application will benefit greatly by following modular patterns, you will loose your code for better maintenance in the future. Can decode in a manner that allows many developers to have different pieces at a time You can work and load your specific modules and addons through the site specific settings file.
I recommend you check Edi Osmani's article on the subject of large scale applications: / P>
-
The moderator, mask, pub / sub patter works very well with modular components, and whatever Modules are like loaders, so you have a good foundation on a large scale applicationI used it on the job and it's a great way to keep everything organized and easy to maintain.
No comments:
Post a Comment