This is just merging the perl stuff into mod_perl, right? Not merging mod_apreq2 and all the request cache/re-play bucket, POST reading, file uploading, etc stuff, right?
I really don't want to have to include mod_perl so my C modules can read POST data and handle file uploads. Cheers, Brian > On Nov 16, 2016, at 4:42 AM, Issac Goldstand <mar...@beamartyr.net> wrote: > > Given that the C was (finally) merged into httpd years ago, and given > that there are no proposed code changes, I'd say that's not such a bad > idea... > > I've become a bit rusty in Perl (and even with apreq) over the years, > but IIRC, all of the Perl glue is in > http://svn.apache.org/repos/asf/httpd/apreq/trunk/glue/perl/ > > I'll take a crack at seeing if I can fold it into mod_perl despite the rust. > > > On 11/15/2016 2:45 PM, Andres Thomas Stivalet wrote: >> Good news!! No idea why apreq hasn't just been merged into mod_perl >> after all these years. >> >> A+++ >> >> On Nov 15, 2016 3:27 AM, "Issac Goldstand" <mar...@beamartyr.net >> <mailto:mar...@beamartyr.net>> wrote: >> >> Hi all, >> >> Someone (finally) noticed that apreq's test suite isn't compatible with >> Apache 2.4 and requested a change. Given that we haven't released an >> updated apreq in nearly 6 years, I'm inclined to make/test the changes >> to the test suite and immediately go to a release cycle. >> >> Does anyone want time to add anything else to libapreq-2.14 before I >> start tarring and voting (in the next few days, I hope)? >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@perl.apache.org >> <mailto:dev-unsubscr...@perl.apache.org> >> For additional commands, e-mail: dev-h...@perl.apache.org >> <mailto:dev-h...@perl.apache.org> >> >
