From 83b2dda8fe710151fada0cf081bb3eb235b6f457 Mon Sep 17 00:00:00 2001
From: Ruediger Pluem mod_dav
. But without a backend provider
which makes use of it, it's useless and should not be loaded into the
server. A sample backend module which actually utilizes
- mod_dav_lock
, is mod_dav_svn, the subversion provider module.
mod_dav_lock
is mod_dav_svn, the subversion provider module.
Note that mod_dav_fs
does not need this
- generic locking module, because it uses it's own more specialized
+ generic locking module, because it uses its own more specialized
version.
In order to make mod_dav_lock
functional, you just have
@@ -49,7 +49,7 @@
In order to retrieve the pointer to the locking provider function, you
have to use the ap_lookup_provider
API with the arguments
- dav-lock
, generic
and 0
.
dav-lock
, generic
, and 0
.
Use the DavGenericLockDB
directive to specify
the full path to the lock database, excluding an extension. If
- the path is not absolute, it will be taken relative to ServerRoot
. The implementation of
+ the path is not absolute, it will be interpreted relative to ServerRoot
. The implementation of
mod_dav_lock
uses a SDBM database to track user
locks.
var/
directory under the ServerRoot
with the base filename
- DavLock
and extension name chosen by the server.
+ DavLock
and an extension added by the server.