model view controller - MVC vs HMVC for web application development -


Now, I am using MVC pattern for web development. I use Codeigner Framework I found and, they are using HMVC, I am still not clear from HMVC and why should we use HMVC instead of MVC? I am confused after reading the HMVC pattern and it is not very different with MVC. Can you understand why we should use HMVC for web application development?

The hierarchical-model-view-controller (HMVC) pattern is a direct extension of the MVC pattern Which manages to solve many scalability issues already mentioned, HMVC was first described in a blog post entitled on the JavaWorld Web site in July. Most of the articles focus on the benefits of using HMVC with a graphical user interface. It has been done that the authors actually re-interpreted another method called Presentation-Abstract-Control (PAC), described in 1987. JavaWorld's article provides detailed explanation how HMVC can assist in the design of desktop applications with GUI. HMVC can be used to create scalable web applications to focus on this article.

HMVC is a collection of traditional MVC trims circulated as an application. Each triad is completely independent and can execute without the presence of any other. All requests made for quarterly should use the controller interface, never load the model or library outside of its own domain. Physical location within the Trivede hosting environment is not important, as long as it is accessible from all other parts of the system. The specific features of HMVC encourage the reuse of existing code, simplifies testing of different parts of the system and ensures that the app is easily enhanced or expanded.



Comments