On Tue, 25 Jun 2002, Ryan Parr wrote: > On June 25, 2002 Robin Berjon wrote: > > So if I were doing that site, the above would look like: > > > > <xsp:page xmlns:xsp="http://apache.org/xsp/core/v1"; > > xmlns:sillytest="http://robin.berjon.com/is/a/dahut/"; > > language="Perl"> > > <sillytest:name-or-form /> > > </xsp:page> > > > > And that would be it. The SillyTest taglib would handle insertion of > either > > <sillytest:prompt-for-name/> or of <sillytest:show-name name='Donald Ahut' > /> > > which would then get transformed by the XSLT stylesheet. > > I'm currently laying out a redesign of the intranet site I use, and am > trying to be very meticulous (though it goes against my nature :). > > I had followed the MVC conversation on the mod_perl list for a little while > and was intrigued, though murky on the more intricate points. Using XSP it > seems that Control is formed from both the XSP page and the taglib itself, > not to mention the ability of the stylesheet to perform some limited control > functions. From a separation and maintenance standpoint, posed to a group > with experience in creating long lived complex sites, would it be better to > let the taglib module handle determining whether or not to send the data or > the form, would it be better handled by the XSP itself, or is the question > ambiguous?
If you really want MVC, then write a taglib and make sure it knows *nothing* about the fact that it's web based (i.e. never use Apache->request). Then your XSP page has to be the controller, the XSLT is the view layer, and the taglib contains the model. This is how I designed AxKit-Wiki, and I've written a pretty clear document on how it's built which you can find on the Wiki: http://axkit.org/wiki -- <!-- Matt --> <:->Get a smart net</:-> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
