Hi Doug,
do you have any plans for supporting mod_dav (which is now part of Apache
2.0) in mod_perl 2.0 ?
The reason for my question is, that I am about to start to write a Perl
interface to mod_dav, so you can create a custom repository (which let you
store data and properties, or manage ACL
good work, let's consider everything before adding new code. below
lays out what i have in mind, combined with your approach...
direct C api mapping
Apache::register_output_filter($filtername, $callback, $filter_type)
Apache::register_input_filter($filtername, $callback,
I'm going to talk about 3 issues here: namespace, prerequisite and CPAN
listing. All related to a single issue, a smooth move into the next
generation of mod_perl with as little confusion created as possible.
=head1 namespace
I think we've discussed this slightly before, but I wonder whether
Hi Doug,
if you implement an interface to mod_dav that works with both 1.x and 2.x,
that would be great and then we can skip the inclusion of an interface
bundled with modperl-2.0. or we could have two, your 1.x version on cpan,
and a 2.x version bundled with modperl-2.0. i'm not sure
On Fri, 25 May 2001, Gerald Richter wrote:
At the moment there are differences, but they aren't so great, but Greg is
about to change the some of the interfaces in 2.0.
My first step would be to implement a version of 1.x (but keep 2.0) in mind
(Because I need it now in a production
