it also solves the problem of “spaghetti code”, you can transfer your HTML / XML / PDF / XSL creation code to your view / template engine, get data from your model (DB / File / RemoteCall, ...), and your controller controls the behavior of both, you can also simply exchange View / Models, without even changing the Controller, if you implement it correctly, so that you get Seperation of Concerncs, improve code and maintainability, and can easily change components are also easier to manage if your projects grow. I recommend using FrontController, which selects the right controller for you, depending on user input, you can also use Inversion of Control / DependencyInjection Pattern, and let your controller be configured with your FrontController / Pass DB connection and lots of lots more fun stuff Now you have simple application framework :) Use Zend instead :)
source share