From: Greg Stein <gstein@apache.org>
Date: Sat, 5 May 2001 11:06:27 +0000 (+0000)
Subject: clarify the use of some of the members of the dav_provider structure.
X-Git-Tag: 2.0.18~103
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=b4f8ab5b11d0414e158ce5fcf1e7169ef1bb002d;p=apache

clarify the use of some of the members of the dav_provider structure.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@89007 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/modules/dav/main/mod_dav.h b/modules/dav/main/mod_dav.h
index 162f7bff66..84df2fdcad 100644
--- a/modules/dav/main/mod_dav.h
+++ b/modules/dav/main/mod_dav.h
@@ -543,9 +543,10 @@ const char *dav_xml_get_cdata(const ap_xml_elem *elem, apr_pool_t *pool,
 ** supply. The provider MUST supply <repos> and <propdb>. The rest are
 ** optional and should contain NULL if that feature is not supplied.
 **
-** Note that a provider cannot pick and choose portions. There are too many
-** dependencies between a dav_resource (defined by <repos>) and the other
-** functionality.
+** Note that a provider cannot pick and choose portions from various
+** underlying implementations (which was theoretically possible in
+** mod_dav 1.0). There are too many dependencies between a dav_resource
+** (defined by <repos>) and the other functionality.
 **
 ** Live properties are not part of the dav_provider structure because they
 ** are handled through the APR_HOOK interface (to allow for multiple liveprop