Time to kill mod_auth_db? More thoughts on using apr-util with auth_dbm.

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

1 files changed, 9 insertions, 1 deletions

diff --git a/STATUS b/STATUS
index fa37012543..1874aae1b4 100644
--- a/STATUS
+++ b/STATUS
@@ -1,5 +1,5 @@
 APACHE 2.0 STATUS:						-*-text-*-
-Last modified at [$Date: 2001/09/15 19:18:59 $]
+Last modified at [$Date: 2001/09/17 02:33:40 $]
 
 Release:
 
@@ -214,6 +214,14 @@ RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
         Justin says: "Seems like this is already there, so should we just 
                       remove the other DBM code in that file?  If you want 
                       to use gdbm, or dbm, etc, you should tell apr-util."
+        Will says: "bs - I may choose the fastest - most efficient native
+                    dbm implementation, for shared proc caches, ssl session
+                    caching, etc, but that has nothing to do with maintaining
+                    a userlist via dbm, which has to remain readable between
+                    builds/machines, etc.  The use-multiple database schema
+                    for apr-util would let us do this with just apr, though."
+
+    * Fold mod_auth_db features back into mod_auth_dbm, and depricate it.
 
     * Integrate mod_dav.
         Some additional items remaining: