Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 92855 invoked from network); 3 Sep 2004 14:12:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 3 Sep 2004 14:12:21 -0000 Received: (qmail 15918 invoked by uid 500); 3 Sep 2004 14:10:34 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 15727 invoked by uid 500); 3 Sep 2004 14:10:26 -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 15632 invoked by uid 99); 3 Sep 2004 14:10:22 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from [84.96.21.10] (HELO mail.anyware-tech.com) (84.96.21.10) by apache.org (qpsmtpd/0.28) with ESMTP; Fri, 03 Sep 2004 07:10:19 -0700 Received: from [10.0.0.170] (unknown [10.0.0.170]) by mail.anyware-tech.com (Postfix) with ESMTP id 0927D5EC1C for ; Fri, 3 Sep 2004 16:10:15 +0200 (CEST) Message-ID: <41387B42.9090908@apache.org> Date: Fri, 03 Sep 2004 16:10:10 +0200 From: Sylvain Wallez User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: fr, en, en-us MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: continuations and session References: <41376984.4020600@mobilebox.pl> <4137957F.3060008@apache.org> <413878FE.9050004@mobilebox.pl> In-Reply-To: <413878FE.9050004@mobilebox.pl> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Leszek Gawron wrote: > Sylvain Wallez wrote: >> Well, IMO the only clean way to achieve this is to have a >> continuations manager that automatically binds new continuations to >> the current session, thus making fully isolated continuation groups. >> >> I proposed this some time ago [1] for other purposes but hadn't the >> time up to now to actually write it. Want to write it? > > If you gave me a few hints what should be changed - I will do it. > Well I started by looking at the CurrentContinuationManagerImpl which is a bit complicated. Maybe writing a new one from scratch would be easier. The idea is to store in the session a data structure that holds the continuations related to the session. This data structure should hold a counter used to create per-session continuation id, and it should also implement HttpSessionBindingListener so that all continuations get properly deleted whenever the continuation expires. Of course, individual continuations should still have their own expiration management. Sorry, not much time lately to help you more on this. Sylvain -- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }