There was some talk on the mod_perl dev list a week or so ago by Gerald Richter of using some of the XS auto generation functionality in mod_perl 2.0 to wrap mod_dav inside perl.
Here is work he has done posted to the web_dav list: http://marc.theaimsgroup.com/?l=dav-announce&m=100139218624911&w=2 Here is the posting the the mod_perl dev list: http://marc.theaimsgroup.com/?l=apache-modperl-dev&m=100141271317363&w=2 Craig On Fri, 5 Oct 2001, tim fulcher wrote: > Hi > > I'm arriving at the conclusion that a few of the things I'm trying to do > in my application are basically pseudo webDAV type actions such as > PROPFIND > & PROPATCH, but currently all handled on the server side via Perl & PHP. > I'm looking to see whether I could move to a proper webDAV type > solution but reuse a lot of the work I've already done. Client side > libraries seem to be reasonably prolific in a number of languages but > server side > implementations are a bit thin on the ground. > > The mod_dav module seems to be a solution of kinds, though people seem > to have lots of hassle getting it to operate alongside mod_perl (indeed > my build of mod_dav as a shared object with mod_perl built statically > prevented the server starting up properly). > But the reason I'd rather not use mod_dav is that I want more control > over how the properties get stored. Ideally I'd want some abstraction to > the > storage layer where I could try out different ideas (Berkeley DB, MySQL > or whatever) to stash the properties (dead ones I guess), plus maybe > lock and version information of resources > > The Jakarta Slide approach seems more akin to what I'm after with webDAV > functionality as just a component, but for now I'd like to stick to > something > in Perl or maybe PHP. > > Frankly I'm surprised no one seems to have attempted a Perl server side > webDAV implementation by now :-) > > Anybody out there tinkered with the possibilities of a mod_perl based > webDAV server ? > > cheers > > > Tim Fulcher >
