View source for Hierarchical model–view–controller

{{Short description|Software design pattern}}
[[File:Pac-schema.png|400px|thumb|right|The structure of an application with [[Presentation-abstraction-control|PAC]].]]
'''Hierarchical model–view–controller''' ('''HMVC''') is a software [[architectural pattern]], a variation of [[model–view–controller]] (MVC) similar to [[presentation–abstraction–control]] (PAC), that was published in 2000 in an article<ref>{{cite web
|last1=Cai |first1=Jason
|last2=Kapila |first2=Ranjit
|last3=Pal |first3=Gaurav
|date=2000-07-21 |df=mdy
|url=https://www.infoworld.com/article/2076128/hmvc--the-layered-pattern-for-developing-strong-client-tiers.html
|title=HMVC: The layered pattern for developing strong client tiers
|work=[[JavaWorld]]
|accessdate=2020-07-18
}}</ref> in [[JavaWorld]] Magazine. The authors were apparently unaware of PAC, which was published 13 years earlier.<ref>{{cite web |author="TP" |date=2000-09-08 |title=Is HMVC PAC? |url=http://www.javaworld.com/javaworld/jw-09-2000/jw-0908-letters.html |archiveurl=https://web.archive.org/web/20060319064042/http://www.javaworld.com/javaworld/jw-09-2000/jw-0908-letters.html |archivedate=2006-03-19 |work=[[JavaWorld]] |df=mdy |department=Letters to the editor}}</ref>
The controller has some oversight in that it selects first the model and then the view, realizing an approval mechanism by the controller. The model prevents the view from accessing the data source directly.
==Example==
The largest practical benefit of using an HMVC architecture is the "widgetization" of content structures.<ref>{{cite web
|author=Vance Lucas
|date=April 2011
|url=https://stackoverflow.com/questions/2263416/what-is-the-hmvc-pattern/5736164#5736165
|title=why HMVC pattern?
|work=[[StackOverflow]]
|accessdate=2013-10-15
}}</ref> An example might be comments, ratings, Twitter or blog RSS feed displays, or the display of shopping cart contents for an e-commerce website. It is essentially a piece of content that needs to be displayed across multiple pages, and possibly even in different places, depending on the context of the main HTTP request.
Traditional MVC frameworks generally do not provide a direct answer for these types of content structures, so programmers often end up duplicating and switching layouts, using custom helpers, creating their own widget structures or library files, or pulling in unrelated data from the main requested Controller to push through to the View and render in a partial. The downside is that the responsibility of rendering a particular piece of content or loading required data leaks into multiple areas and gets duplicated in the respective places.
HMVC, or specifically the ability to dispatch sub-requests to a Controller to handle these responsibilities aims to solve this problem. The structure mimics that of traditional MVC. For example, if one needs to load some data about comments, and display them in HTML format, one would send a request to the comments Controller with some parameters. The request then interacts with the Model, picks a View, which displays the content. The difference from a traditional MVC is that instead of displaying the comments in a fully separate page, they are displayed inline below the article the user is viewing. In this regard, HMVC strives to increase code [[Modular programming|modularity]], aid reusability, and maintain a better separation of concerns.
==See also==
* [[Presentation–abstraction–control]] (PAC)
* [[Model–view–controller]] (MVC)
==References==
<references />
{{DEFAULTSORT:Hierarchical model-view-controller}}
[[Category:Software analysis patterns]]