Mailing-List: contact apreq-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Mail-Followup-To: apreq-dev@httpd.apache.org
To: apreq-dev@httpd.apache.org
From: Joe Schaefer <joe+gmane@sunstarsys.com>
Subject: Re: cvs commit: httpd-apreq-2/build xsbuilder.pl
Date: 31 Oct 2003 08:24:37 -0500
Lines: 32
Message-ID: <m33cd9fskq.fsf@sol.sunstarsys.com>
References: <20031030044552.83594.qmail@minotaur.apache.org>
 <3FA0B411.7050402@stason.org> <m3he1qg6ra.fsf@sol.sunstarsys.com>
 <3FA15443.50007@stason.org> <m3d6cefrbe.fsf@sol.sunstarsys.com>
 <Pine.LNX.4.56.0310310010010.22145@theoryx5.uwinnipeg.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Mail-Copies-To: never
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
Sender: news <news@sea.gmane.org>

Randy Kobes <randy@theoryx5.uwinnipeg.ca> writes:

[...]

> Until things are arranged so that all the needed APR::* can
> be used outside of mp2, I've been looking at the perl glue
> in a CGI context, just to see what's involved. This entails
> having available mod_perl.so as an so/dll. Although this may
> not be the best model, I tried the following, just to see if
> it works:

Cool.

> - make an Apreq::Base, consisting of a Base.xs that just
> made available apr_initialize() and apr_terminate2().
> - make an Apreq::Request which loads Apreq::Base and has
> a new() method to create an Apreq::Request object by
>     - calling apr_initialize()
>     - creating a $p = APR::Pool->new()
>     - creating a $req = Apache::Request->new($p, @_)
> - make an Apreq::Cookie which similarly passes a $p pool
> in as the $env within Apache/Cookie.pm.
> - I'm not sure about this, but I also made a DESTROY sub
> which calls apr_terminate2().

initialize/terminate are per-process events, so calling them
from the object ctor/dtor is probably a mistake.  IMO those calls
probably belong inside BEGIN and END blocks within APR.pm.
If that were so, Base.xs would be unnecessary, right?

-- 
Joe Schaefer