comments on a showstopper

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

diff --git a/STATUS b/STATUS
index 275e76a4608efcdd043e29cc90f535df691afab6..344e9f20cbde7172c6e9291be18f5f40d4c6535f 100644 (file)
--- a/STATUS
+++ b/STATUS
@@ -1,5 +1,5 @@
 APACHE 2.0 STATUS:                                              -*-text-*-
-Last modified at [$Date: 2002/03/08 17:49:05 $]
+Last modified at [$Date: 2002/03/08 21:34:20 $]
 
 Release:
 
@@ -62,6 +62,12 @@ FINAL RELEASE SHOWSTOPPERS:
         Jim asks: would a stopgap be something bogus like adding another
         flag to request_rec ala eos_sent and before we OK, if not set
         force 500?
+        Jeff says: reviewing the original message and the one
+        follow-up (also from OtherBill) it looks like OtherBill had a
+        good handle on the problem, though I wonder why not just put a
+        simple check in default_handler to see if dir/file_walk has
+        been done (a footprint left by dir/file_walk doesn't have to
+        be in request_rec; a better place is core_request_config)
 
     * We need to find out the right place to add the AddOutputFilterByType
       directive.  mod_mime?  No.  core with fixups?  That's what it is now.