Geert Josten wrote: > Wikipedia actually disagrees > (http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller, > paragraph 6 and 7), but to me that is counter intuitive. I > would say that at least the Model is typically a kind of > Singleton in the entire organisation. And it would make most > sense to me if there would be only one Controller per web > application. Activities in one part of the web application > typically affect behavior in other parts. And I could imagine > that you don't always want to rely on a shared model for that..
Well, yes, each page has a triplet model+view+controller, from a design perspective. But from an engineering point of view, the controller can be the same component for several pages (if not for all pages). About the model, for a web application developped within the MarkLogic HTTP app server this is simple: the model is the database, that you access and manipulate "directly" :-) Regards, -- Florent Georges http://www.fgeorges.org/ _______________________________________________ General mailing list [email protected] http://xqzone.com/mailman/listinfo/general
