Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 36825 invoked from network); 8 Aug 2005 10:15:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 8 Aug 2005 10:15:47 -0000 Received: (qmail 73651 invoked by uid 500); 8 Aug 2005 10:15:44 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 73612 invoked by uid 500); 8 Aug 2005 10:15:43 -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 73598 invoked by uid 99); 8 Aug 2005 10:15:42 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Aug 2005 03:15:42 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [64.49.223.165] (HELO chandler.sharp.fm) (64.49.223.165) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Aug 2005 03:16:06 -0700 Received: by chandler.sharp.fm (Postfix, from userid 48) id 543FD932A9A; Mon, 8 Aug 2005 05:15:41 -0500 (CDT) Received: from 196.8.104.31 (SquirrelMail authenticated user minfrin@sharp.fm); by www.sharp.fm with HTTP; Mon, 8 Aug 2005 12:15:41 +0200 (SAST) Message-ID: <40891.196.8.104.31.1123496141.squirrel@www.sharp.fm> In-Reply-To: References: Date: Mon, 8 Aug 2005 12:15:41 +0200 (SAST) Subject: Re: how to make sub-requests? From: "Graham Leggett" To: dev@httpd.apache.org Cc: dev@httpd.apache.org User-Agent: SquirrelMail/1.4.3a-12.EL4 X-Mailer: SquirrelMail/1.4.3a-12.EL4 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Parin Shah said: > - using make_sub_request, ap_sub_req_method_uri methods. these > functions create a new request_req for a sub request and they take > current request_req as one of the argument. but mod-cache-requester > may not have current request available. I suspect the best idea here is to create a bare bones request_req on demand, and then use this same request_req for all the subrequests to be fetched in that batch. > we can store the original request_req which was used when the page was > served from cache, and then use it as a parameter to the above method. > Is this approach is fine? This isn't very clean, a request_req is just a structure, they should be relatively simple to make. Look for the code within the core that brings the request_req into existence for the first time, you should be able to see how it gets created. Regards, Graham --