Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 95171 invoked from network); 29 Oct 2004 10:53:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 29 Oct 2004 10:53:56 -0000 Received: (qmail 48820 invoked by uid 500); 29 Oct 2004 10:53:40 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 48766 invoked by uid 500); 29 Oct 2004 10:53:39 -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 48749 invoked by uid 99); 29 Oct 2004 10:53:39 -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 [195.216.81.146] (HELO helios.otego.com) (195.216.81.146) by apache.org (qpsmtpd/0.28) with SMTP; Fri, 29 Oct 2004 03:53:37 -0700 Received: (qmail 10091 invoked from network); 29 Oct 2004 10:53:35 -0000 Received: from helios.otego.com (HELO localhost) (192.168.222.204) by helios.otego.com with SMTP; 29 Oct 2004 10:53:35 -0000 Date: Fri, 29 Oct 2004 12:53:34 +0200 (CEST) From: Giacomo Pati X-X-Sender: giacomo@lapgp.otego.com To: dev@cocoon.apache.org Subject: RE: Implementation of the Continuations checker Message-ID: X-GPG-FINGRPRINT: D216 25E0 084A 9090 9BF4 1EC0 3710 05D8 BA4A 9F94 X-GPG-PUBLIC_KEY: http://pks.gpg.cz:11371/pks/lookup?op=get&search=0x371005D8BA4A9F94 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Fri, 29 Oct 2004, Carsten Ziegeler wrote: > Giacomo Pati wrote: >> >> On Fri, 29 Oct 2004, Carsten Ziegeler wrote: >> >>> The current implementation of our continuations manager uses the >>> excalibur event package for the background checker that checks for >>> expired continuations. >>> >>> Now, this approach has the problem, that excalibur event is >>> deprecated. In addition we aren't using it somewhere else, >> so it would >>> be great if we could remove this dependency. >>> >>> Yesterday, I wrote a simple replacement which I checked into 2.2: >>> a simple background thread is initialized that sleeps for a >> configured >>> period of time, checks the continuations, sleeps etc. >>> Now, this solution should work. >>> >>> The question is now, should I port this to 2.1.x as well? Are there >>> better solutions? >> >> Does this mean the CommandManager from the Context is gone? >> > Yes, at least for 2.2 - for 2.1.x we would have to decide if we remove it. > > Are you using it? Yes, we used the CommandManager in some projects. It is based on the PooledExecutor from Doug Leas concurrent-utils package. It comes in quite handy as you can put tasks there you'd like to be done asynchroniously (ie. indexing a uploaded document with lucene to speed up percieved performance). One alternative is that we build up our own CommandManager into the Context which is piece of cake to do. -- Giacomo Pati Otego AG, Switzerland - http://www.otego.com Orixo, the XML business alliance - http://www.orixo.com