cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giacomo Pati <giac...@apache.org>
Subject Re: defaulting to a matcher when another one is not present
Date Tue, 08 Oct 2002 19:36:08 GMT
tcurdt@dff.st wrote:
>>>Could you do a
>>>
>>><map:match pattern="*">
>>>  <map:redirect-to uri="../not-found"/>
>>></map:match>
>>>
>>>or something as last one and cascade the way up?
>>
>>This should work as well, except that it makes another round-trip to 
>>the client browser: ugly!
> 
> 
> you could also use a resource - then it should be an internal redirect...
> 
> btw: do we already have an "always" matcher?
> due to the lastest performance analysis we should better
> substitute
> 
> <map:match pattern="*"> or <map:match pattern="**">
> 
> with 
> 
> <map:match type="always">

Well, you might end up with Matchers like

    <map:match type="startsWith" pattern="foo">

or

    <map:match type="endsWith" pattern="bar">

for performance reasons and the numbers of Matchers will exponantially grow.

Giacomo


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message