Maybe we should try it out. It shouldn't be that difficult to adapt what goes on in the servlet to a filter.
-----Original Message----- From: Geoff Longman [mailto:[EMAIL PROTECTED] Sent: Saturday, March 11, 2006 2:16 PM To: Tapestry development Subject: Re: TapestryFilter... I had thought about that in the past too. It's a neat idea. Can't think of any downsides off the top of my head other than there might be a perception by some that a Filter is a lower class entity to a Servlet. Geoff On 3/10/06, James Carman <[EMAIL PROTECTED]> wrote: > All, > > I had an idea the other day that I voiced on the user list, but I wanted to > hear some feedback from the real gurus! What if we changed the way Tapestry > is implemented from an actual servlet to a servlet filter? The > filter-mapping could be "/*" so that it would intercept ALL requests. If > the request corresponds to a service, then the filter will delegate to the > service to handle it. If it doesn't, then it just lets it pass right by. > That way, we could enable "friendly URLs" easily without having to change > the web.xml file. Thoughts? > > James > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- The Spindle guy. http://spindle.sf.net Get help with Spindle: http://lists.sourceforge.net/mailman/listinfo/spindle-user Blog: http://jroller.com/page/glongman Feature Updates: http://spindle.sf.net/updates --------------------------------------------------------------------- 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]
