From: Chris Pepper Date: Tue, 3 Jun 2008 03:11:16 +0000 (+0000) Subject: Minor cleanup on DAV Locking module. X-Git-Tag: 2.3.0~552 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=24b9c32485de0e4750702cd630136b97a32af177;p=apache Minor cleanup on DAV Locking module. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@662627 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mod_dav_lock.xml b/docs/manual/mod/mod_dav_lock.xml index 60b55153c5..60dfa111f7 100644 --- a/docs/manual/mod/mod_dav_lock.xml +++ b/docs/manual/mod/mod_dav_lock.xml @@ -35,11 +35,11 @@ the service of 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_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 @@ -50,7 +50,7 @@ Developer's Note

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.

mod_dav @@ -66,7 +66,7 @@

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 mod_dav_lock uses a SDBM database to track user locks.

@@ -83,7 +83,7 @@ an existing directory. In the above example, Apache will create files in the 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.