httpd-apreq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Peters <mpet...@plusthree.com>
Subject Re: [multi-env] perl glue status
Date Mon, 11 Apr 2005 17:29:07 GMT
Joe Schaefer wrote:
> Michael Peters <mpeters@plusthree.com> writes:
> 
> 
>>Joe Schaefer wrote:
> 
> 
> [...]
> 
> 
>>>How about something like this?
>>>    use APR::Request::Apache2 compat => "apreq1";
>>>This would then provide Apache::Request, Apache::Cookie, and
>>>Apache::Upload.   They'd be identical to the current
>>>Apache2:: modules in the multi-env branch.
>>
>>Or maybe let someone else split it off as a separate project
>>to just maintain those perl modules?
> 
> 
> Heh, that's what got us into this mess ;-).
> You still have to contend with libapreq1's existing
> modules, which are appropriately enjoying bitrot; 
> but they aren't being eol'd.

Well, maybe splitting off Apache2::Request, Apache2::Upload, 
Apache2::Cookie as a separate, perl project so that will just follow 
libapreq2 and libapreq2 doesn't need to concern itself with them.

-- 
Michael Peters
Developer
Plus Three, LP


Mime
View raw message