Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 49496 invoked from network); 5 May 2009 20:48:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 5 May 2009 20:48:24 -0000 Received: (qmail 65634 invoked by uid 500); 5 May 2009 20:48:23 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 65568 invoked by uid 500); 5 May 2009 20:48:22 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 65559 invoked by uid 99); 5 May 2009 20:48:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 May 2009 20:48:22 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.9] (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 05 May 2009 20:48:20 +0000 Received: (qmail 49029 invoked by uid 2161); 5 May 2009 20:46:43 -0000 Received: from [192.168.2.4] (euler.heimnetz.de [192.168.2.4]) by cerberus.heimnetz.de (Postfix on SuSE Linux 7.0 (i386)) with ESMTP id 6CB851721C for ; Tue, 5 May 2009 22:46:33 +0200 (CEST) Message-ID: <4A00A5AF.2080109@apache.org> Date: Tue, 05 May 2009 22:46:39 +0200 From: Ruediger Pluem User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.21) Gecko/20090402 SeaMonkey/1.1.16 MIME-Version: 1.0 To: dev@httpd.apache.org Subject: Re: mod_proxy / mod_proxy_balancer References: <49FFFCB5.7060701@gmail.com> <4A003FF6.5090509@gmail.com> <4A005213.9040904@apache.org> <4A0057B1.5000803@gmail.com> <4A00644B.9050509@gmail.com> <1342264E-706D-4D6C-B123-89C8A07AC543@jaguNET.com> <4A0074FC.500@gmail.com> <678D1F35-6228-41C6-B09A-E1F2B330B848@jaguNET.com> <4A008D39.6040508@gmail.com> <4A00A48C.1020908@gmail.com> In-Reply-To: <4A00A48C.1020908@gmail.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org On 05/05/2009 10:41 PM, jean-frederic clere wrote: > > The next question is how do we call the ageing? > - Via a thread that calls it after an elapsed time. More accurate, but more complex. > - When there is a request and the actual time is greater than the time Less accurate, but less complex. I tend to say lets go with this approach. It works even for non threaded MPMs, seems accurate enough on a somewhat busy system and isn't that complex as with a separate thread. Regards Rüdiger