> -Original Message-
> From: Graham Leggett [mailto:minf...@sharp.fm]
> Sent: Sonntag, 8. März 2015 16:47
> To: d...@httpd.apache.org
> Cc: apreq-dev@httpd.apache.org
> Subject: Re: Was there any concrete decision on apreq?
>
> On 08 Mar 2015, at 9:11 AM,
On Mar 8, 2015, at 11:46 AM, Graham Leggett wrote:
>
> For ages library functions for httpd have ended up in APR, but this isn’t
> ideal - APR is a portability layer, and even though code is being accepted
> that “works with APR”, in reality we really need a libhttpd library that can
> provide
In a nutshell the long term goal has always been to get the c parts of apreq
incorporated into httpd distributions so the perl parts can ship with modperl.
This is still along those lines. In order to continue to expose the cool cgi
code that Issac added to libapreq we need to ensure there is
I think nothing.
Most mod_perl users (I think) install apreq via Apache2::Request. That
can continue to be maintained on CPAN, as is, linking against httpd
instead of mod_apreq
Or do you forsee a problem here?
On 2/24/2015 9:56 AM, Steve Hay wrote:
> What would this mean for mod_perl users? I,
