On Fri, 2006-03-10 at 12:16 +0100, Grzegorz Kossakowski wrote:
> Hello Bertrand,
>
> Friday, March 10, 2006, 11:51:33 AM, you wrote:
>
> > Le 10 mars 06 à 11:31, hepabolu a écrit :
>
> > Just wondering about this isGlobal explanation:
>
> > "If the isGlobal argument is true, the redirect will be global, i.e.
> > it returns all the way to the browser, even from within internal
> > requests."
>
> > is not too clear for me, I'd write:
>
> after few moments of exhilaration caused by the fact my first reported bug
> was fixed I feel the same, it's not clear
>
> > "The isGlobal argument, if true, causes an HTTP redirect to be sent
> > to the client browser in all cases.
>
> > When isGlobal is false and the current request is an internal one
> > (i.e. uses the cocoon: protocol), the redirect is processed
> > internally within Cocoon, by executing the pipeline specified by the
> > uri argument, without sending an HTTP redirect".
>
> +1 for this with one exception. Not always pipeline is executed even isGlobal
> is
> false. Eg:
> <map:aggregate>
> <map:part src="cocoon:/callflow"/>
> </map:aggregate>
>
> And in some flow function:
> cocoon.redirectTo("http://www.google.com";, false);
>
> Aggregator will try to use as a part content read from google. So it's not
> neccessarily redirect to another Cocoon pipeline. It just redirect internal
> request to whatever you want.
Thanks for clarifying (I learned something new). I added your
explanation to the docs:
http://cocoon.zones.apache.org/daisy/legacydocs/documentation/userdocs/flow/api.html
--
Bruno Dumon http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
[EMAIL PROTECTED] [EMAIL PROTECTED]
