On Tuesday 25 June 2002 06:58, Ryan Parr wrote: There are certain issues with considering a webapp to be an MVC model. The nature of both HTML and HTTP often conspire to make the seperation unclean. For instance there are certain aspects of forms which have implications both for the appearance AND the functionality of the form. As an example, in a textarea is the WRAP attribute properly site logic or site style? It has implications for both, and that makes it hard to decide how and where to choose its value...
Certain other common web page constructs have similar and sometimes even more complex issues, such as the frequently seen "click here for the next 10 search results" or any of the 100's of situations where you have javascript and server side logic interacting. Not to say MVC is an invalid way of looking at a webapp, but you will find that factoring the 3 aspects into seperate code modules with well-defined boundaries is virtually impossible in some cases. > 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? > > -- Ryan > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
