cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sylvain Wallez <sylv...@apache.org>
Subject Re: Continuation invalidation strategy
Date Mon, 02 May 2005 16:47:55 GMT
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.

Sylvain

-- 
Sylvain Wallez                        Anyware Technologies
http://apache.org/~sylvain            http://anyware-tech.com
Apache Software Foundation Member     Research & Technology Director


Mime
View raw message