You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apreq-dev@httpd.apache.org by Joe Schaefer <jo...@sunstarsys.com> on 2005/04/14 16:11:26 UTC
[VOTE] Re: [multi-env] perl glue status
Joe Schaefer <jo...@sunstarsys.com> writes:
> Joe Schaefer <jo...@sunstarsys.com> writes:
>
>> Ok, here's what I propose to do with the branch:
>>
>> 1) Move Apache2::Request::upload() to APR::Request::upload().
[...]
> OTOH, instead of (2), maybe we could continue to distribute them,
> and transfer those to mp2 when the time is right. Would that make
> more sense than dropping them right now?
Let's make a decision on this so we can move forward.
I'm +1 for taking the above route. If the mod_perl team
rejects our Apache2::* modules after httpd has accepted
the C API, that's when I'll favor dropping those.
--
Joe Schaefer
Re: [VOTE] Re: [multi-env] perl glue status
Posted by "Philip M. Gollucci" <pg...@p6m7g8.com>.
Michael Peters wrote:
>>Let's make a decision on this so we can move forward.
>>
>>I'm +1 for taking the above route. If the mod_perl team
>>rejects our Apache2::* modules after httpd has accepted
>>the C API, that's when I'll favor dropping those.
>>
>>
>
>+1
>
>
+1
--
END
-----------------------------------------------------------------------------
Philip M. Gollucci
Senior Developer - Liquidity Services Inc.
Phone: 202.568.6268 (Direct)
E-Mail: pgollucci@liquidation.com
Web: http://www.liquidation.com
Re: [VOTE] Re: [multi-env] perl glue status
Posted by Michael Peters <mp...@plusthree.com>.
Joe Schaefer wrote:
> Joe Schaefer <jo...@sunstarsys.com> writes:
>
>
>>Joe Schaefer <jo...@sunstarsys.com> writes:
>>
>>
>>>Ok, here's what I propose to do with the branch:
>>>
>>> 1) Move Apache2::Request::upload() to APR::Request::upload().
>
>
> [...]
>
>
>>OTOH, instead of (2), maybe we could continue to distribute them,
>>and transfer those to mp2 when the time is right. Would that make
>>more sense than dropping them right now?
>
>
> Let's make a decision on this so we can move forward.
>
> I'm +1 for taking the above route. If the mod_perl team
> rejects our Apache2::* modules after httpd has accepted
> the C API, that's when I'll favor dropping those.
+1
--
Michael Peters
Developer
Plus Three, LP
Re: [VOTE] Re: [multi-env] perl glue status
Posted by Joe Schaefer <jo...@sunstarsys.com>.
Geoffrey Young <ge...@modperlcookbook.org> writes:
> Joe Schaefer wrote:
>> If the mod_perl team
>> rejects our Apache2::* modules after httpd has accepted
>> the C API, that's when I'll favor dropping those.
>
> sorry for dropping in on the conversation at a very late date...
>
> what exactly might mod_perl reject? using the Apache2:: namespace
> without being a core mp2 module? I don't see a problem with that.
Me neither; I'm just trying to balance the decision-making
sequence so there's no pressure on any other communities to
make a hasty decision. We're sort of in a bind here with
the recent mp2 rename (our trunk is now defective, the
multi-env branch ain't ready yet, and our prior releases
don't work with mp2's latest candidate). IOW, the pressure
on *us* to release 2.05-dev has grown considerably now, but
that shouldn't negatively impact *other* ASF communities.
--
Joe Schaefer
Re: [VOTE] Re: [multi-env] perl glue status
Posted by Geoffrey Young <ge...@modperlcookbook.org>.
Joe Schaefer wrote:
> If the mod_perl team
> rejects our Apache2::* modules after httpd has accepted
> the C API, that's when I'll favor dropping those.
sorry for dropping in on the conversation at a very late date...
what exactly might mod_perl reject? using the Apache2:: namespace without
being a core mp2 module? I don't see a problem with that.
--Geoff
Re: [VOTE] Re: [multi-env] perl glue status
Posted by Randy Kobes <ra...@theoryx5.uwinnipeg.ca>.
On Thu, 14 Apr 2005, Philip M. Gollucci wrote:
> Jonathan Vanasco wrote:
> > Wouldn't it make more sense to have APR as a namespace
> > under Apache/Apache2 ?
>
> I think you meant to say:
> Apache2::APR::*
The Apache/Apache2 top-level namespace usually is tied to
mod_perl, particularly mod_perl.so. However, although at
present the APR::* modules needed by apreq2 are contained
within the mp2 distribution, these particular modules can be
used without mod_perl.so (see the t/apr-ext tests in mp2).
This allows, for example, apreq2 to work within cgi scripts;
at one point, someone even got it to work with a non-Apache
web server.
--
best regards,
randy
Re: [VOTE] Re: [multi-env] perl glue status
Posted by "Philip M. Gollucci" <pg...@p6m7g8.com>.
Jonathan Vanasco wrote:
>Wouldn't it make more sense to have APR as a namespace under
Apache/Apache2 ?
I think you meant to say:
Apache2::APR::*
--
END
-----------------------------------------------------------------------------
Philip M. Gollucci
Senior Developer - Liquidity Services Inc.
Phone: 202.568.6268 (Direct)
E-Mail: pgollucci@liquidation.com
Web: http://www.liquidation.com
Re: [VOTE] Re: [multi-env] perl glue status
Posted by Joe Schaefer <jo...@sunstarsys.com>.
Jonathan Vanasco <jv...@mastersofbranding.com> writes:
> Unless I'm mistaken, none of the perl glue works without mod_perl --
> so having Apache2/APR would logically chain the dependencies
You are mistaken. Most of the perl glue depends only on the APR stuff
in mod_perl. We already have stand-alone cgi tests for APR::Request::CGI.
--
Joe Schaefer
Re: [VOTE] Re: [multi-env] perl glue status
Posted by Jonathan Vanasco <jv...@mastersofbranding.com>.
Well, what I mean was really this:
Wouldn't it make more sense to have APR as a namespace under
Apache/Apache2 ?
Unless I'm mistaken, none of the perl glue works without mod_perl -- so
having Apache2/APR would logically chain the dependencies
I thought it was currently Apache::APR -- which makes sense to me.
From what I'm reading, it looks like the suggested change is to make
the APR library on the same node level as Apache
On Apr 14, 2005, at 1:13 PM, Joe Schaefer wrote:
> The other way, APR::Request::Apache2::upload(), might be possible;
> but that'd require adding Apache2::RequestRec to
> @APR::Request::Apache2::ISA.
> FWIW, I don't think that's a good idea, so unless upload() is 100%
> portable IMO it should stay where it is.
Re: [VOTE] Re: [multi-env] perl glue status
Posted by Joe Schaefer <jo...@sunstarsys.com>.
Jonathan Vanasco <jv...@mastersofbranding.com> writes:
> On Apr 14, 2005, at 10:11 AM, Joe Schaefer wrote:
>>>> 1) Move Apache2::Request::upload() to APR::Request::upload().
>
> Can the perl glue be used outside of the mod_perl environment?
Hmm, looking at that upload() code, the only problem I see here
is with the $req->pool call in the last line. We don't provide
an pool struct anymore, so that call's inherited from Apache2::RequestRec.
So I guess moving upload() across to APR::Request::upload() is
a no-go for now; I'll just leave it where it is.
> If so, then I'm +1
>
> If not, would it be less confusing if it were
> Apache2::APR::Request::upload() ?
The other way, APR::Request::Apache2::upload(), might be possible;
but that'd require adding Apache2::RequestRec to @APR::Request::Apache2::ISA.
FWIW, I don't think that's a good idea, so unless upload() is 100%
portable IMO it should stay where it is.
--
Joe Schaefer
Re: [VOTE] Re: [multi-env] perl glue status
Posted by Jonathan Vanasco <jv...@mastersofbranding.com>.
On Apr 14, 2005, at 10:11 AM, Joe Schaefer wrote:
>>> 1) Move Apache2::Request::upload() to APR::Request::upload().
Can the perl glue be used outside of the mod_perl environment?
If so, then I'm +1
If not, would it be less confusing if it were
Apache2::APR::Request::upload() ?