Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (asf.osuosl.org: domain of parin.soc@gmail.com designates
 64.233.162.204 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=MiTca/Zv/R2/3VvP/S2zHsyqn8XZkebjRD23JPL91C5GjK12PsHj2Lm10uzN/mBGbnHQqmZ4A2V6V6C5NCTXaP5nYX4MFNWN7lVC8NI2scOheGbuL9/CUGoLSyz71MbpCLV6YoOUjzc5eAqoqtNCjDSUkNTSRhPLz0aQgTIxNpM=
Message-ID: <e0f6a050050809065814968043@mail.gmail.com>
Date: Tue, 9 Aug 2005 08:58:51 -0500
From: Parin Shah <parin.soc@gmail.com>
To: dev@httpd.apache.org
Subject: Re: how to make sub-requests?
In-Reply-To: <6.2.1.2.2.20050808054310.05353120@pop3.rowe-clan.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <e0f6a050050805220141e76787@mail.gmail.com>
	 <40891.196.8.104.31.1123496141.squirrel@www.sharp.fm>
	 <6.2.1.2.2.20050808054310.05353120@pop3.rowe-clan.net>

Thanks for your replies.

There is a way to create a request rec using function:
ap_read_request(conn_rec *).

now conn_rec could be created using ap_run_create_connection function
which takes pool, socket, bucket and some other arguments. I waasnt
sure how to get socket information  as we cannot use the connection of
any current request_rec for that.

It would be really helpful if you can suggest me some pointers for this.

Thanks,
Parin.

On 8/8/05, William A. Rowe, Jr. <wrowe@rowe-clan.net> wrote:
> At 05:15 AM 8/8/2005, Graham Leggett wrote:
> >Parin Shah said:
> >
> >> 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.
>=20
> Actually I'd suggest you use the core to create that request_rec,
> rather than chasing upgrades for all the things you need to add
> custom when the structure changes.  The request_rec can and does
> grow on mmn minor bumps, so that's an extra reason to avoid ever
> allocating one yourself.  You will have very minimal ABI compat
> if you allocate your own, and should probably emit a warning on
> startup if you see the mmn minor has moved.
>=20
> Bill
>=20
>=20
>