Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 77270 invoked from network); 3 May 2005 06:31:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 3 May 2005 06:31:22 -0000 Received: (qmail 28218 invoked by uid 500); 3 May 2005 06:32:08 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 28110 invoked by uid 500); 3 May 2005 06:32:07 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 28032 invoked by uid 99); 3 May 2005 06:32:06 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from smtp003.mail.ukl.yahoo.com (HELO smtp003.mail.ukl.yahoo.com) (217.12.11.34) by apache.org (qpsmtpd/0.28) with SMTP; Mon, 02 May 2005 23:32:06 -0700 Received: from unknown (HELO ?192.168.1.31?) (reinhard?poetz@62.178.239.20 with plain) by smtp003.mail.ukl.yahoo.com with SMTP; 3 May 2005 06:30:20 -0000 Message-ID: <42771A76.5000801@apache.org> Date: Tue, 03 May 2005 08:30:14 +0200 From: Reinhard Poetz User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: Continuation invalidation strategy References: <4275DF46.2020408@apache.org> <4275FA3B.2070402@mobilebox.pl> <42760323.7080804@apache.org> <427659BB.3010904@apache.org> <42765DBB.1030803@mobilebox.pl> <4276A189.8090409@apache.org> In-Reply-To: <4276A189.8090409@apache.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Sylvain Wallez wrote: > Leszek Gawron wrote: > >> Sylvain Wallez wrote: >> >>> Reinhard Poetz wrote: >> >> > > > >>>> 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? > > > > The Rhino scope, which is a rather important piece of information :-) The Rhino scope is still in the user's session and only deleted when the session is invalidated and shouldn't be affected by invalidating a continuation, AFAIU. Right? -- Reinhard P�tz Independent Consultant, Trainer & (IT)-Coach {Software Engineering, Open Source, Web Applications, Apache Cocoon} web(log): http://www.poetz.cc --------------------------------------------------------------------