On Fri, 30 May 2003, Mike Whittaker wrote:
> Date: Fri, 30 May 2003 19:09:47 +0100 > From: Mike Whittaker <[EMAIL PROTECTED]> > Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]> > To: Struts Users Mailing List <[EMAIL PROTECTED]> > Subject: RE: time to do action > > > > > >Maybe I'm wrong, but this is how I understand the way filters work. > > You are probably right, my brain hurts, it's Friday. > > > > >> I want the Struts way, I'm learning struts. > > > >I didn't realize there was a Struts way. Filters are filters, aren't they? > > > > There must be a struts way to do it surely. You could certainly create a custom RequestProcessor that includes timing if you wanted to, but filters are a much more elegant mechanism to accomplish this particular thing (timing a request). We shouldn't assume that Struts (or any other framework) is going to meet 100% of your needs. After all, Struts doesn't try to solve your persistence-tier problems; it comfortably integrates with anything you would like to use. In the same way, you can easily integrate non-Struts tag libraries, non-Struts XML parsing and processing, non-Struts servlets, non-Struts filters ... we should enjoy the synergy of using these things together instead of hoping for a "mother of all frameworks" solution that satisfies every single need in one package. Craig --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
