cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sylvain Wallez <sylvain.wal...@anyware-tech.com>
Subject Re: Errorhandling for internal requests
Date Thu, 10 Apr 2003 14:40:23 GMT
juergen.seitz@basf-it-services.com wrote:

>Hi Sylvain,
>
>we like the idea with the subprotocol and are going to implement it
>

Wait, wait : it's the solution that I like the less, and I really would 
like to have others opinions before going any further. You know, it's 
called "community consensus".

Sylvain

>What's the difference between
>  <map:redirect-to uri="cocoon://blah">
>and
>  <map:generate src="cocoon://blah">
>  <map:serialize/>
>
>Not that much, in fact... I don't think your use case can be considered
>as a general behaviour that should be "hardcoded" in the sitemap engine.
>
>If we need to tell externally to the called pipeline if it should handle
>errors or not, this should go through the URI. We can either use a
>particular subprotocol (e.g. "cocoon:handle-errors://blah"), or an
>additional request parameter (e.g.
>"cocoon://blah?cocoon-handle-errors=false"). I like the second solution
>more, but we must take great care that this parameter is allowed only
>internally to avoid any security hole.
>
>But I'm still not sure it's good to control error-handling behaviour
>from the oustide. At least we must have it from the inside.
>
>What do others think ?
>
>Sylvain
>  
>

-- 
Sylvain Wallez                                  Anyware Technologies
http://www.apache.org/~sylvain           http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }



Mime
View raw message