Thanks, that helps a lot!

I forgot to ask...what happens when a continuation is no longer valid and the user clicks on a link that would activate a continuation?  Does the element simply begin execution at the beginning of processElement()?  If so, is there a way for the element to know that it's starting over from an invalid continuation?

I did set up not to clone continuations for paging, since paging isn't really sensitive to context: just give me the new offset, though I suppose cloning continuations would let the user page through multiple result sets...I really did it because I was tired of chasing down the CloneNotSupportedExceptions, but maybe that's a worthy pursuit after all.

Thanks,

-Alf


On 6/3/06, Geert Bevin <[EMAIL PROTECTED]> wrote:
Hi Alf,

it's a good question!

RIFE has a WeakHashMap with the continuation ids and their
references, continuations also have a default timeout of 20 minutes,
after which they will become illegible for purging, which happens by
default 1 out of 50 requests (this is of course configurable).
Besides that you, can also setup each element to not clone
continuations if you don't need that behavior, and last, when a user
finished a flow, you can remove the entire active continuation tree
and thus all related state.

Hope this helps,

Geert


_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users

Reply via email to