----- Original Message ----- From: "Craig R. McClanahan" <[EMAIL PROTECTED]> To: "Struts Developers List" <[EMAIL PROTECTED]> Sent: Monday, April 08, 2002 9:21 AM Subject: Re: Servlet 2.3 filter
> > > On Sun, 7 Apr 2002, Martin Cooper wrote: > > > Date: Sun, 7 Apr 2002 21:34:37 -0700 > > From: Martin Cooper <[EMAIL PROTECTED]> > > Reply-To: Struts Developers List <[EMAIL PROTECTED]> > > To: Struts Developers List <[EMAIL PROTECTED]> > > Subject: Re: Servlet 2.3 filter > > > > [snip] > > I attended Kevin's session, and chatted with him afterwards. The model he > > described is one where the request URL points directly to the JSP page > > itself, and the controller does the preparation necessary to display that > > page. > > > > However, this model really only works for simple applications. One example > > in which this breaks is where some action needs to be taken in addition to > > displaying the JSP page, and there is no one-to-one relationship between the > > action and the page. (In Struts-land, this is the equivalent of having > > multiple actions which may forward to the same JSP page.) > > > > <ducking-for-cover> > In other words, Kevin pitched a Model 1 design with the business logic in > a filter instead of inside the page? :-) > </ducking-for-cover> Yup, I guess that's actually a pretty good way of summarising it, although I'm sure he wouldn't be too happy with that description... ;-) -- Martin Cooper > > > Kevin realises now that this is a problem with the approach he presented. > > I'm sure he'll be giving it more thought, though. ;-) > > > > -- > > Martin Cooper > > > > Craig > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
