"Sylvain Wallez" <[EMAIL PROTECTED]> wrote:
> Pier, unless I'm mistaken, it seems your problem can be solved with the
> flow without hacking sessions.
Indeed... But Stefano asked "Should the flow _always_ be associated with a
Session?", which I assumed (maybe prematurely) as a one-to-one mapping
between session and flow, therefore reducing the number of flows in
execution by the client, as we have only one session...
> A continuation tree is actually the "flow instance" you're talking
> about. So you can have different flow instances running concurrently
> smoothly, provided that their state is only stored in local variables.
>
> Global variables should be used to represent state that is
> user-dependent but not flow-dependent.
>
> What do you think ?
I'm fine w/ it, as long as the continuation ID is never stored in the
session, but rather always URL encoded in the generated output...
That's the only thing I'm _really_ concerned about...
Pier
