Christian Parpart <[EMAIL PROTECTED]> writes:
> my problem is not the extra depend on apreq, but what I can't find really
> neat, is, that it seems to be a perl module (based on mod_perl somehow) and
> IIRC, mod_transform shouldn't be overbloated by depends that itself
> depend on too much the actual project (here: mod_transform) doesn't need.
>
> Sorry for being a n00b regarding libapreq, so here my quick question:
> can you build it w/o the mod_perl depend?
Yes, in fact the default is to not build the mod_perl glue; you have
to explicitly pass --enable-perl-glue to configure to build that.
> At least the homepage[1] looks promising in its feature set as it (in
> fact) does what we need right now.
>
> secondly: is libapreq able to retrieve POST arguments from a filter module,
> specifically mod_transform?
Yes, what mod_transform needs to do is create a filter-init function
that invokes apreq_handle_apache2 (it's actually a faq, see
<URL:http://svn.apache.org/repos/asf/httpd/apreq/trunk/
module/t/c-modules/apreq_output_filter_test/
mod_apreq_output_filter_test.c>
for an example output filter with a filter-init function.
--
Joe Schaefer
