Leszek Gawron wrote:
>
> Hello,
> Christofer Oliver has written [1] that I should make a
> proposal so here it is:
>
> What do you think about the flow ability to call a
> continuation knowing the continuation id.
>
> It should look something like:
>
> contManager = null;
> try {
> contManager = cocoon.getComponent(
> "org.apache.cocoon.components.flow.ContinuationsManager" );
> var wk = contManager.lookupWebContinuation( continuationId
> ); } finally {
> if ( contManager != null )
> cocoon.releaseComponent( contManager );
> }
>
> cocoon.handleContinuation( wk.getContinuation(), wk );
>
> Right now this is not a supported feature (it works when one
> does not use page local variables).
>
Hmm, I'm not sure what to think about this, but:
> The usage:
> - when he continuation id is stored somewhere else than
> request uri (for
> example request parameter)
This can be done very easy. Change the place where you create
the link and change the "getting the cont. id" logic in the
sitemap by using a different input module.
> - when one gets 2 continuation ids and chooses one basing on
> some external
> info
Can you give an example, when you need this? - Just curious.
> - when one wants to do something for each continuation
> resumed (for example
> set "Cache-control" header).
Can you expand a little bit more on this?
>
> For all above examples you have to code logic in sitemap. I
> think this is not as elegant as if you could have whole logic
> in a flowscript
>
At the current state of this discussion I would say, let's not
add this feature to flow. If you want to do such things, write
some custom components (input modules, actions etc.) and use
them at appropriate places. But perhaps with some more info,
I see things in different light.
Carsten
