Return-Path: 
 <dev-return-48225-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-dev-archive@www.apache.org
Received: (qmail 10884 invoked from network); 26 Sep 2003 09:02:34 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 26 Sep 2003 09:02:34 -0000
Received: (qmail 43861 invoked by uid 500); 26 Sep 2003 09:01:52 -0000
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 43797 invoked by uid 500); 26 Sep 2003 09:01:51 -0000
Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@cocoon.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@cocoon.apache.org>
list-post: <mailto:dev@cocoon.apache.org>
Reply-To: dev@cocoon.apache.org
Delivered-To: mailing list dev@cocoon.apache.org
Received: (qmail 43768 invoked from network); 26 Sep 2003 09:01:50 -0000
Received: from unknown (HELO trinity.anyware-tech.com) (217.112.237.100)
  by daedalus.apache.org with SMTP; 26 Sep 2003 09:01:50 -0000
Received: (qmail 27851 invoked from network); 26 Sep 2003 09:02:03 -0000
Received: from unknown (HELO anyware-tech.com) (10.1.0.254)
  by trinity.anyware-tech.com with SMTP; 26 Sep 2003 09:02:03 -0000
Message-ID: <3F74008D.5060807@anyware-tech.com>
Date: Fri, 26 Sep 2003 11:02:05 +0200
From: Sylvain Wallez <sylvain.wallez@anyware-tech.com>
Organization: Anyware Technologies
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.4) Gecko/20030624
X-Accept-Language: fr, en, en-us
MIME-Version: 1.0
To: users@cocoon.apache.org
CC: dev@cocoon.apache.org
Subject: Re: Flowscript problem?
References: <007001c38409$60d41630$1e01a8c0@WRPO>
In-Reply-To: <007001c38409$60d41630$1e01a8c0@WRPO>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Reinhard Poetz wrote:

>>From: Sylvain Wallez
>>    
>>
<snip/>

>>I was also thinking about having ContinuationLocal variables that would mimic the behaviour of InheritableThreadLocal for continuations.
>>
>>This would handle the use cases where a variable's value should not be shared between continuations : when the value is fetched, crawl up the continuation tree up to a point where a value exists, and when the value is set, attach it only to the forthcoming continuation (not to the latest one, as it may be the root of a continuation subtree).
>>    
>>
>
>Sounds good! This would be the feature Francis is asking for, wouldn't it?
>  
>

Yes, and it would allow to "pay the cost" for this behaviour only when 
it's really needed.

Sylvain

-- 
Sylvain Wallez                                  Anyware Technologies
http://www.apache.org/~sylvain           http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
Orixo, the opensource XML business alliance  -  http://www.orixo.com