Sylvain Wallez wrote:
Reinhard Poetz wrote:
Leszek Gawron wrote:
Reinhard Poetz wrote:
Today I've had a look at continuation invalidation. I found
following code fragment in the ContinuationManagerImpl:
// REVISIT: This places only the "leaf" nodes in the expirations
Sorted Set.
// do we really want to do this?
if (parent.getChildren().size() < 2) {
expirations.remove(parent);
}
Is it right that this means that only if a leaf continuation
expires, the continuations tree is walked up and parent
continuations are checked whether they have expired?
Yes, all children continuation have to expire for the parent to be
removed.
Are there any problems if a parent continuation is removed before its
children, except that the user can't jump back?
The execution state of a continuation is dependent on it's parent state.
So although we may trash parent webcontinuations (i.e. the enveloppe
used by the continuation manager), we must ensure that a strong link
exists with the parent state.
Looks like there is something I am not aware of. What 'state' do you
refer to. What would have happened if you just sent parent continuation
to null?
--
Leszek Gawron [EMAIL PROTECTED]
IT Manager MobileBox sp. z o.o.
+48 (61) 855 06 67 http://www.mobilebox.pl
mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
