You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by br...@apache.org on 2012/11/28 08:22:54 UTC

svn commit: r1414561 - /subversion/branches/in-repo-authz/BRANCH-README

Author: breser
Date: Wed Nov 28 07:22:53 2012
New Revision: 1414561

URL: http://svn.apache.org/viewvc?rev=1414561&view=rev
Log:
On in-repo-authz branch: Update BRANCH-README

* BRANCH-README: Fill in work left to do and some thoughts on tests.

Modified:
    subversion/branches/in-repo-authz/BRANCH-README

Modified: subversion/branches/in-repo-authz/BRANCH-README
URL: http://svn.apache.org/viewvc/subversion/branches/in-repo-authz/BRANCH-README?rev=1414561&r1=1414560&r2=1414561&view=diff
==============================================================================
--- subversion/branches/in-repo-authz/BRANCH-README (original)
+++ subversion/branches/in-repo-authz/BRANCH-README Wed Nov 28 07:22:53 2012
@@ -3,3 +3,34 @@ authz allows authz configuration files t
 
 The design for this code is here:
 http://wiki.apache.org/subversion/InRepoAuthz
+
+TODO
+
+* svnserve - I have partial support written, but need to deal with the whole
+    --config-file issue.
+* tests - Need to finish writing the tests for svn_repos_authz_read2().
+    It's not really feasable to handle DAV testing with the way our test
+    suite is currently written.  We have two authz directives and 4 different
+    styles of authz paths.  So we'd need 8 different Location's to be setup,
+    which seems absurd to me.  One alternative is to migrate to always using
+    something akin to davautocheck.
+* schemas - non file URL schemas should error.
+* errors - DAV error messages kinda suck since it guesses what it thinks is
+    the best error message at current.  When it should display the whole chain.
+* svnauthz-validate - Needs to be adjusted accordingly.
+* refactor svn_repos_authz_read* functions to share a common implementation. 
+* documentation - as in the user level docs.
+
+TESTS
+
+Following tests should be developed (+ means we should look for success,
+- means we should look for failure).
+
++ absolute path on OS file system.
++ relative path on OS file system.
++ file:// url to repo path.
++ relative path in repo (^/)
+- http:// url
+- svn:// url
+- OS path that does not exist
+- repo path that does not exist