Offer more thoughts

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

1 files changed, 19 insertions, 1 deletions

diff --git a/ROADMAP b/ROADMAP
index c8e9854201..83806713c1 100644
--- a/ROADMAP
+++ b/ROADMAP
@@ -1,6 +1,6 @@
 APACHE 2.x ROADMAP:
 
-Last modified at [$Date: 2002/10/01 13:28:31 $]
+Last modified at [$Date: 2002/10/01 13:55:00 $]
 
 DEFERRRED FOR APACHE 2.1
 
@@ -89,19 +89,37 @@ MAKING APACHE REPOSITORY-AGNOSTIC
       (backwards compat: today, when this occurs with mod_dav and a
        custom backend, the above items refer to the topmost directory
        mapped by a location; e.g. docroot)
+
+      Need to preserve a 'filename'-like string for mime-by-name
+      sorts of operations.  But this only needs to be the name itself
+      and not a full path.
     
     * The translate_name hook goes away
+
+      Wrowe altogether disagrees.  translate_name today even operates
+      on URIs ... this mechansim needs to be preserved.
     
     * The doc for map_to_storage is totally opaque to me. It has
       something to do with filesystems, but it also talks about
       security and per_dir_config and other stuff. I presume something
       needs to happen there -- at least better doc.
 
+      Wrowe agrees and will write it up.
+
     * The directory_walk concept disappears. All configuration is
       tagged to Locations. The "mod_filesystem" module might have some
       internal concept of the same config appearing in multiple
       places, but that is handled internally rather than by Apache
       core.
+
+      Wrowe suggests this is wrong, instead it's private to filesystem
+      requests, and is already invoked from map_to_storage, not the core
+      handler.  <Directory > and <Files > blocks are preserved as-is,
+      but <Directory > sections become specific to the filesystem handler
+      alone.  Because alternate filesystem schemes could be loaded, this
+      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>
     
     * The "Location tree" is an in-memory representation of the URL
       namespace. Nodes of the tree have configuration specific to that