Hi David (and others)! Just popping in to echo Micah's link to xqmvc
and mention that it implements several of the issues you've brought up
in this thread.
http://code.google.com/p/xqmvc/wiki/START_HERE
Feel free to peruse the codebase as well:
http://code.google.com/p/xqmvc/source/browse/
If there is interest, and ideas/visions of what such a framework should
do are fairly close, perhaps we can work together to produce something
greater than the sum of its parts.
Cheers,
Eric
Geert Josten wrote:
DAG Florent! ;-)
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..
Kind regards,
Geert
Drs. G.P.H. Josten
Consultant
http://www.daidalos.nl/
Daidalos BV
Source of Innovation
Hoekeindsehof 1-4
2665 JZ Bleiswijk
Tel.: +31 (0) 10 850 1200
Fax: +31 (0) 10 850 1199
http://www.daidalos.nl/
KvK 27164984
De informatie - verzonden in of met dit emailbericht - is afkomstig van
Daidalos BV en is uitsluitend bestemd voor de geadresseerde. Indien u dit
bericht onbedoeld hebt ontvangen, verzoeken wij u het te verwijderen. Aan dit
bericht kunnen geen rechten worden ontleend.
From: [email protected]
[mailto:[email protected]] On Behalf Of
Florent Georges
Sent: dinsdag 15 december 2009 18:42
To: General Mark Logic Developer Discussion; Micah Dubinko
Subject: Re: [MarkLogic Dev General] Towards a more modular
app architecture ...
Micah Dubinko wrote:
In terms of app architecture XQMVC is definitely worth a look:
http://code.google.com/p/xqmvc/
And then there's my take...
http://dubinko.info/blog/2009/11/29/model-endpoint-template/
Interesting, thanks for the links Micah!
Just a little note: your post seems to imply each page in
an MVC application has a triplet model+view+controller.
IMHO, in modern MVC frameworks, you only have a couple of
controllers, the main job of which being to decide which
model to use, and which view to apply on it (even if, as I
said, I think there is not really such things as pure models
and pure views, but instead a panel of "things" ranging from
model to view).
Regards,
--
Florent Georges
http://www.fgeorges.org/
_______________________________________________
General mailing list
[email protected]
http://xqzone.com/mailman/listinfo/general
_______________________________________________
General mailing list
[email protected]
http://xqzone.com/mailman/listinfo/general
_______________________________________________
General mailing list
[email protected]
http://xqzone.com/mailman/listinfo/general
