Return-Path: Delivered-To: apmail-httpd-modules-dev-archive@minotaur.apache.org Received: (qmail 28442 invoked from network); 15 Jul 2009 14:23:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Jul 2009 14:23:08 -0000 Received: (qmail 73518 invoked by uid 500); 15 Jul 2009 14:23:18 -0000 Delivered-To: apmail-httpd-modules-dev-archive@httpd.apache.org Received: (qmail 73474 invoked by uid 500); 15 Jul 2009 14:23:17 -0000 Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: modules-dev@httpd.apache.org Delivered-To: mailing list modules-dev@httpd.apache.org Received: (qmail 73464 invoked by uid 99); 15 Jul 2009 14:23:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Jul 2009 14:23:17 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Jul 2009 14:23:07 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1MR5Ne-00025K-6r for modules-dev@httpd.apache.org; Wed, 15 Jul 2009 07:22:46 -0700 Message-ID: <24498988.post@talk.nabble.com> Date: Wed, 15 Jul 2009 07:22:46 -0700 (PDT) From: ricardo13 To: modules-dev@httpd.apache.org Subject: Re: How do I manipulate request_rec Object in worker.c In-Reply-To: <1247661698.20095.1@raydesk1.bettercgi.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: ricardoogrande@gmail.com References: <24496166.post@talk.nabble.com> <1247661698.20095.1@raydesk1.bettercgi.com> X-Virus-Checked: Checked by ClamAV on apache.org Ray Morris wrote: > >> I modified request_rec simply adding a field in >> request_rec. Now, I would like get this field >> in worker.c > > You also wouldn't modify request_rec, adding > a new data member, to add information about a > request anyway. If you wanted to add information > about a request, you would add it to the notes > table if there were no appropriate existing member. > request rec is used by every other module, so you > have no right to go changing it's definition. > > If you're wanting to prioritize by IP address, > Google "QOS" and your OS, such as "QOS Linux". > If you're wanting to prioritize based on something > else, start with r->connection. > > r->connection ?? How ?? > > Thank you > Ricardo > > -- > Ray Morris > support@bettercgi.com > > Strongbox - The next generation in site security: > http://www.bettercgi.com/strongbox/ > > Throttlebox - Intelligent Bandwidth Control > http://www.bettercgi.com/throttlebox/ > > Strongbox / Throttlebox affiliate program: > http://www.bettercgi.com/affiliates/user/register.php > > > On 07/15/2009 06:39:11 AM, ricardo13 wrote: >> >> hi all, >> >> I modified request_rec simply adding a field in request_rec. >> Now, I would like get this field in worker.c >> >> My doubt about this is because worker.c manipulates only sockets and >> doesn't >> request_rec object. >> How do I do this ?? >> >> Thank you >> Ricardo >> >> -- >> View this message in context: http://www.nabble.com/How-do-I- >> manipulate-request_rec-Object-in-worker.c-tp24496166p24496166.html >> Sent from the Apache HTTP Server - Module Writers mailing list >> archive >> at Nabble.com. >> >> > > > > -- View this message in context: http://www.nabble.com/How-do-I-manipulate-request_rec-Object-in-worker.c-tp24496166p24498988.html Sent from the Apache HTTP Server - Module Writers mailing list archive at Nabble.com.