httpd-apreq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Schaefer <joe+gm...@sunstarsys.com>
Subject Re: cvs commit: httpd-apreq-2/build xsbuilder.pl
Date Fri, 31 Oct 2003 13:24:37 GMT
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


Mime
View raw message