cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vadim Gritsenko <va...@reverycodes.com>
Subject Re: svn commit: r111262 - in cocoon/branches/BRANCH_2_1_X/src: java/org/apache/cocoon/components/flow webapp/WEB-INF
Date Fri, 10 Dec 2004 14:01:06 GMT
Leszek Gawron wrote:
> Vadim Gritsenko wrote:
> 
>> Leszek Gawron wrote:
>>
>>>
>>> Previously we have discussed about three continuations manager work 
>>> modes:
>>>
>>> - standard (current functionality)
>>> - continuations invalidated along with session, still the continuation
>>> is reachable from other sessions (or no session at all)
>>> - fully isolated. only the session that created the continuation can
>>> access it.
>>>
>>> Thing is after a while I still do not see a use case for a second 
>>> case where continuations would be invalidated with user session but 
>>> still accessibe for everyone (of course before invalidation). So I 
>>> have changed the continuations manager to support only 1st and 3rd case.
>>>
>>> about 2nd: YAGNI (thanks Stefano for new cool phrase :))
>>
>>
>>
>> I thought 1st was older functionality, 2nd was current functionality 
>> (with sitemap isolation, not sessions). 2nd as you formulated it is 
>> not needed, 100% agreement here.
>>
> 
> Not quite. Sitemap isolation is implied for EVERY case.

Currently - yes. But not at the time when discussion was made. I was referring 
to the older discussion.


> If the user has 
> a site that he/she is not able to refactor the old behaviour may be 
> enabled by setting continuation-sharing-bug-compatible to true.

I know.

Vadim

Mime
View raw message