Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>In Kohana, at least, an HMVC request is a HTTP request that is serviced "internally": instead of being issued over the network, it's routed, dispatched and handled by the framework itself. The similarity of the names "HMVC" and "MVC" is confusing in that it suggests an underlying connection between the terms that does not in fact exist: one is not a minor variant or modification of the other, they are completely different things. (HMVC is also described as Ajax without the client-side HTTP request.) Kohana's emphasis on, and support for "HMVC" means that the framework has strong support for a HTTP-based service oriented architecture.</p> <p>The advantage of this architectural pattern is that since the same "calling convention" is used for internal and external requests, it's trivial to convert "internal" service requests to "external" requests or vice versa as the need arises.</p> <p>Whilst this is a sensible architectural pattern, giving it its own name seems unnecessary (Symfony2 describes the same concept "<a href="http://symfony.com/doc/current/book/controller.html#forwarding" rel="nofollow noreferrer">sub-requests</a>"), and in fact the name seems to be a misnomer: there's no particular requirement or need that the requests form a hierarchy (other than the standard call graph of every imperative program); the requests could easily be recursive, for example.</p> <p>[<strong>Update Apr 2011, Mar 2012:</strong> Expanded on answer in response to comments.]</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload