cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ovidiu Predescu <ovi...@apache.org>
Subject Re: [control flow] changes and new sample
Date Sat, 07 Sep 2002 00:32:00 GMT
Hi Ramy,

On Friday, September 6, 2002, at 11:02 AM, Ramy Mamdouh wrote:

> Hello,
>
> Being working on a project that uses the Control Flow extensively, 
> made me a big fan of this great piece of software.

This is great! Please do let me know if you encounter any problems with 
it.

> However, I have some comments here :
>
> 1- sendPage() and the cocoon:/ protocol :
>
> As I stated before, why the enforcement of using the "cocoon:/" 
> protocol inside AbstractInterpreter.forwardTo() to make the 
> redirection??

Sorry, I forgot about this. Thanks for reminding me about it.

> ---
> PipelinesNode.getRedirector(environment)
>        .redirect(false, "cocoon:/" + URI);
> ---
> This enforces any URI passed to the sendPage() to use the cocoon:/ 
> protocol, which doesn't work for some situations.
> For example, I couldn't use the Portal framework with it as far as I 
> tested.
> And currently I've changed the above method to make the protocol 
> optional, meaning that the caller to sendPage() specify also the 
> protocol to be used in redirection, I also had to save the 
> continuation ID in session when the cocoon:/ protocol is not used.
> So, I'm thinking that the sendPage() shouldn't enforce the use of the 
> cocoon:/ protocol, what do you think?

Can you please explain in more detail what the problem was with the 
redirection using the cocoon:/ protocol and the Portal framework? I 
don't see where an issue could appear. You almost always want the page 
to be redirected to an internal pipeline.

Perhaps a better solution is to remove the "cocoon:/" string from the 
AbstractInterpreter.forwardTo() method and put it in the system.js 
sendPage() function, which at least could be redefined. What do you 
think?

> 2- XSP :
>
> On the project I'm working on, we don't use XSP.
> And so, we don't have any means to get the Continuation ID, thus We've 
> made a simple ContinuationTransformer and ContinuationAction that 
> makes using the Control Flow possible for not XSP based applications.

This is nice, would you care to contribute them?

> Finally, Although I consider Cocoon is a really magical thing, I do 
> think that the Flow Control is one of the most exciting stuff I've 
> seen since I knew about web programming.

Oh, thank you very much! I'm glad you like the concept, I'll try to 
improve it even more.

Best regards,
-- 
Ovidiu Predescu <ovidiu@apache.org>
http://webweavertech.com/ovidiu/weblog/ (Weblog)
http://www.geocities.com/SiliconValley/Monitor/7464/ (Apache, GNU, 
Emacs ...)


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


Mime
View raw message