Return-Path: Delivered-To: apmail-httpd-modules-dev-archive@minotaur.apache.org Received: (qmail 76143 invoked from network); 15 Jul 2009 12:42:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Jul 2009 12:42:03 -0000 Received: (qmail 58482 invoked by uid 500); 15 Jul 2009 12:42:12 -0000 Delivered-To: apmail-httpd-modules-dev-archive@httpd.apache.org Received: (qmail 58450 invoked by uid 500); 15 Jul 2009 12:42:12 -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 58440 invoked by uid 99); 15 Jul 2009 12:42:12 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Jul 2009 12:42:12 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of support@bettercgi.com designates 216.17.105.202 as permitted sender) Received: from [216.17.105.202] (HELO ps536.phatservers.com) (216.17.105.202) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Jul 2009 12:42:01 +0000 Received: from r74-192-24-94.bcstcmta01.clsttx.tl.dh.suddenlink.net ([74.192.24.94] helo=raydesk1.bettercgi.com) by ps536.phatservers.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.66) (envelope-from ) id 1MR3no-0006g6-2h for modules-dev@httpd.apache.org; Wed, 15 Jul 2009 05:41:40 -0700 Date: Wed, 15 Jul 2009 07:41:38 -0500 From: Ray Morris Subject: Re: How do I manipulate request_rec Object in worker.c To: modules-dev@httpd.apache.org In-Reply-To: <24496166.post@talk.nabble.com> (from ricardoogrande@gmail.com on Wed Jul 15 06:39:11 2009) X-Mailer: Balsa 2.3.26 Message-Id: <1247661698.20095.1@raydesk1.bettercgi.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org > I modified request_rec simply adding a field in=20 > request_rec. Now, I would like get this field=20 > in worker.c You also wouldn't modify request_rec, adding=20 a new data member, to add information about a=20 request anyway. If you wanted to add information=20 about a request, you would add it to the notes=20 table if there were no appropriate existing member. request rec is used by every other module, so you=20 have no right to go changing it's definition. If you're wanting to prioritize by IP address,=20 Google "QOS" and your OS, such as "QOS Linux". If you're wanting to prioritize based on something=20 else, start with r->connection. -- 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: >=20 > hi all, >=20 > I modified request_rec simply adding a field in request_rec. > Now, I would like get this field in worker.c >=20 > My doubt about this is because worker.c manipulates only sockets and > doesn't > request_rec object. > How do I do this ?? >=20 > Thank you > Ricardo >=20 > --=20 > 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=20 > archive > at Nabble.com. >=20 >=20