Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 21152 invoked from network); 13 Jul 2006 16:22:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 13 Jul 2006 16:22:32 -0000 Received: (qmail 83644 invoked by uid 500); 13 Jul 2006 16:22:28 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 83593 invoked by uid 500); 13 Jul 2006 16:22:27 -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 83582 invoked by uid 99); 13 Jul 2006 16:22:27 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Jul 2006 09:22:27 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of jfclere@gmail.com designates 64.233.182.189 as permitted sender) Received: from [64.233.182.189] (HELO nf-out-0910.google.com) (64.233.182.189) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Jul 2006 09:22:27 -0700 Received: by nf-out-0910.google.com with SMTP id i2so261633nfe for ; Thu, 13 Jul 2006 09:22:05 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=ciOa6fLb7zp9uKlmqJx9tt/gI5p8zpkIUsSXANdAghzW0gb/7gzMwKbdhFct83vL0WGeWD8MV++dynL1Aao/GHHtNpZng912GstJa81rOsimR3N83DakWG1dIlDyBOZw8l/W2ICVKlQl0yOe1HzRkvLTyJbMci0hATL8JWdglmw= Received: by 10.48.226.15 with SMTP id y15mr1077238nfg; Thu, 13 Jul 2006 09:22:05 -0700 (PDT) Received: from ?192.168.4.43? ( [217.8.202.234]) by mx.gmail.com with ESMTP id c10sm3458550nfb.2006.07.13.09.22.05; Thu, 13 Jul 2006 09:22:05 -0700 (PDT) Message-ID: <44B67322.8070302@gmail.com> Date: Thu, 13 Jul 2006 18:21:54 +0200 From: Jean-frederic Clere User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.13) Gecko/20060417 X-Accept-Language: en, fr MIME-Version: 1.0 To: dev@httpd.apache.org Subject: Re: Additing a storage for the shared information of the worker in mod_proxy References: <44B576AF.6080303@gmail.com> <44B579AA.1080205@turner.com> <5D8F9212-834B-4E18-AC7E-9A4008C634BD@jaguNET.com> <44B65285.8070901@turner.com> <44B66CD5.5050508@gmail.com> <44B66DC7.5040103@turner.com> In-Reply-To: <44B66DC7.5040103@turner.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Brian Akins wrote: > Jean-frederic Clere wrote: > >> With such an interface you assume only one process will access to one >> slot... That is what the scoreboard allows. >> Allowing updates from different proccesses on the same slot. >> Should we have an ap_slot_read_look() and an ap_slot_unlock() for that? > > > No. we don't have such for the "built-in" scoreboard. Anything can > read the scoreboard, only current "worker slot" can change it. that's > why in the "sample" API, to get the memory you pass a conn_rec. > > If it's slow, people won't use it. Semaphores are generally "slow." > Enforcing it by convention like we currently do seems reasonable. > The workers shared information is shared by the processes already, all the processes may access the same slot or I am complety wrong? Cheers Jean-Frederic