i was born a rambling man...

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

diff --git a/ROADMAP b/ROADMAP
index b7ad575dcd51ddf83444429fb12ba9e960d7fcd5..6e5c48649e48a23ab18b7ae8652051d60e0208ea 100644 (file)
--- a/ROADMAP
+++ b/ROADMAP
@@ -1,6 +1,6 @@
 APACHE 2.x ROADMAP:
 
-Last modified at [$Date: 2002/10/01 16:51:10 $]
+Last modified at [$Date: 2002/10/01 19:13:06 $]
 
 DEFERRRED FOR APACHE 2.1
 
@@ -113,7 +113,15 @@ MAKING APACHE REPOSITORY-AGNOSTIC
               should get fully resolved. None of this "resolve to
               <here> and then we have a magical second resolution
               (inside the CGI script)" or somesuch.
-    
+   
+      Justin: Well, let's consider mod_mbox for a second.  It is sort of
+              a virtual filesystem in its own right - as it introduces
+              it's own notion of a URI space, but it is intrinsically
+              tied to the filesystem to do the lookups.  But, for the
+              portion that isn't resolved on the file system, it has
+              its own addressing scheme.  Do we need the ability to
+              layer resolution?
+
     * The translate_name hook goes away
 
       Wrowe altogether disagrees.  translate_name today even operates
@@ -140,7 +148,9 @@ MAKING APACHE REPOSITORY-AGNOSTIC
       should be exposed, from the core, for other file-based stores to 
       share. Consider an archive store where the layers become 
       <Directory path> -> <Archive store> -> <File name>
-    
+   
+      Justin: How do we map Directory entries to Locations?
+ 
     * The "Location tree" is an in-memory representation of the URL
       namespace. Nodes of the tree have configuration specific to that
       location in the namespace.
@@ -216,3 +226,13 @@ MAKING APACHE REPOSITORY-AGNOSTIC
               it? eeewwwww...
               
               I'll vote -0.9 for CGIs as a filter. Keep 'em handlers.
+
+      Justin: So, do we give up executing CGIs from virtual repositories?
+              That seems like a sad tradeoff to make.  I'd like to have
+              my CGI scripts under DAV (SVN) control.
+
+    * How do we handle overlaying of Location and Directory entries?
+      Right now, we have a problem when /cgi-bin/ is ScriptAlias'd and
+      mod_dav has control over /.  Some people believe that /cgi-bin/
+      shouldn't be under DAV control, while others do believe it
+      should be.  What's the right strategy?