Hierarchical model–view–controller

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[1] in JavaWorld Magazine, the authors apparently unaware[2] of PAC, which was published 13 years earlier.

The structure of an application with PAC.

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.[3] 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 modularity, aid reusability, and maintain a better separation of concerns.

gollark: https://github.com/python/cpython/blob/fa2eee975dbf7d2728021ef9d97328bbe88351cf/Modules/_randommodule.c#L266
gollark: The `super().seed(a)` function it passes stuff onto may be doing things internally.
gollark: You can pass it things which aren't actually ints.
gollark: I think the python `random.seed` thing runs the seed you use through a bunch of weird processes including SHA512 and stuff, instead of just directly seeding the RNG with it.
gollark: Because why *not* ship an entire gigantic browser with every application?

See also

References
  1. Cai, Jason; Kapila, Ranjit; Pal, Gaurav (July 21, 2000). "HMVC: The layered pattern for developing strong client tiers". JavaWorld. Retrieved 2020-07-18.
  2. "TP" (September 8, 2000). "Is HMVC PAC?". Letters to the editor. JavaWorld. Archived from the original on 2006-03-19.
  3. Vance Lucas (April 2011). "why HMVC pattern?". StackOverflow. Retrieved 2013-10-15.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.