You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by James Carman <ja...@carmanconsulting.com> on 2006/03/10 19:08:59 UTC
TapestryFilter...
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: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: TapestryFilter...
Posted by James Carman <ja...@carmanconsulting.com>.
I might be able to try to put a few cycles towards this. I've never even
built Tapestry before, so it'll take me a couple of days to get moving,
though.
> Seems worth a try, anyone know where we can find a patch? ;)
>
> On 3/11/06, James Carman <ja...@carmanconsulting.com> wrote:
>>
>> 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:glongman@gmail.com]
>> 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 <ja...@carmanconsulting.com> 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: tapestry-dev-unsubscribe@jakarta.apache.org
>> > For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>> >
>> >
>>
>>
>> --
>> 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: tapestry-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>>
>>
>
James Carman, President
Carman Consulting, Inc.
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: TapestryFilter...
Posted by Jesse Kuhnert <jk...@gmail.com>.
Seems worth a try, anyone know where we can find a patch? ;)
On 3/11/06, James Carman <ja...@carmanconsulting.com> wrote:
>
> 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:glongman@gmail.com]
> 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 <ja...@carmanconsulting.com> 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: tapestry-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
> >
> >
>
>
> --
> 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: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
>
RE: TapestryFilter...
Posted by James Carman <ja...@carmanconsulting.com>.
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:glongman@gmail.com]
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 <ja...@carmanconsulting.com> 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: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
>
--
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: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: TapestryFilter...
Posted by Geoff Longman <gl...@gmail.com>.
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 <ja...@carmanconsulting.com> 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: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
>
--
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: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org