httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Stein <>
Subject Re: cvs commit: httpd-2.0/modules/dav/lock config6.m4
Date Mon, 06 Jan 2003 22:10:55 GMT
On Mon, Jan 06, 2003 at 06:42:51PM -0000, wrote:
> jerenkrantz    2003/01/06 10:42:51
>   Modified:    modules/dav/lock config6.m4
>   Log:
>   Um, that should have been a 'no' - you should have to explicitly enable
>   mod_dav_lock not always include it whenever mod_dav is built.

The other thing that could happen is to enable locking services *only* when
the DAVGenericLockDB directive is present. However, that will change mod_dav
a bit, as it assumes that locking *is* available if the hooks are available.
The hooks would need to be expanded with an "enabled?" query function.

That allows you to build in mod_dav_lock, yet not force people to add a new
directive simply because other DAV providers now see the module.

btw, note that mod_dav_lock is still maintaining the notion of a "key type"
(inode vs fname). That isn't required any more. Another question: does it
record a file name or a location name?


Greg Stein,

View raw message