Re: mod_python as a mod_dav backend

[Graham Dumpleton]

On 02/02/2006, at 6:52 AM, Deron Meranda wrote:

Actually it seems that this is yet another case of trying to get
mod_python to hook into more places in the Apache framework;
specifically to hook into other modules.

We've already been discussing specific-module hooks for

  mod_ssl - http://issues.apache.org/jira/browse/MODPYTHON-94

  mod_include - http://issues.apache.org/jira/browse/MODPYTHON-104

In fact there's a bit of potentially useful discussion in the notes
for those JIRA issues which is valid for any module-hooking in general
(along with this mailing list archives).  I'd say it might be
worthwhile to at least create a new feature-request issue for mod_dav
hooks though; just so it's on the record.

Adding in support for mod_ssl and mod_include was reasonably trivial
and a natural fit for the basic functionality of mod_python.

Support for mod_dav development using Python would be a considerable
amount of work as it involves construction of a range of new Python  
wrapper
classes for C structures and call in infrastructure for Python which  
would be
quite tailored for that purpose. Having mod_dav support goes far  
beyond the
basic charter of what mod_python is about and all this extra work  
would be
an undue burden on core mod_python developers and cause even more
delays in any releases.

Thus why I see that you would be better of having a separate project for
a mod_dav_python module. There would still be changes required in
mod_python to allow the separate module to hook into the basic  
infrastructure,
but this would be a more practical way of going about it and would also
allow other distinct modules besides mod_dav_python to be developed
which could have bindings for Python.

Graham