From: "Sander van Zoest" <[EMAIL PROTECTED]> Sent: Monday, January 07, 2002 12:48 PM
> On Mon, 7 Jan 2002, Ryan Bloom wrote: > > > On Sunday 06 January 2002 11:55 pm, Sander van Zoest wrote: > > > On Mon, 7 Jan 2002, William A. Rowe, Jr. wrote: > > > > > > > From: "Ryan Bloom" <[EMAIL PROTECTED]> > > > > > I would like to discuss the reasoning behind this change. Why are we trying > > > > > to overload the meaning of DocumentRoot this way? > > > > Because it allows the DocumentRoot to be, well, nonexistant. > > > This is very useful in environments where you want an URI space that > > > doesn't necessarily line up with anything on a file system. > > > This would be very useful for things such as mod_perl, XML/XSLT solutions, > > > RTSP/Icecast servers, etc. > > Huh? We already have a way to do all of that. In fact, all this does is add >another > > way to configure options that already exist. > > So, you are saying that I can create an apache httpd daemon where it would never >make a > stat(2) in the default DocumentRoot directory? > > If so, let me know how, because that would be really useful. As Ryan suggested, you can do that _today_ if you are the module author. Catch the map_to_storage hook, say HOOK_MIDDLE, and return OK if the request matches your module's critera. Since map_to_storage is run-first, your OK will confirm that it finished configuring the r->per_dir_config, and dir_walk/file_walk are skipped (they are HOOK_LAST). If you aren't the module author, you have to wait for us to finish debating this patch, and for Sander to grok the 'unset' directive :) Bill
