On Monday 07 January 2002 05:14 am, William A. Rowe, Jr. wrote: > From: "William A. Rowe, Jr." <[EMAIL PROTECTED]> > Sent: Monday, January 07, 2002 12:06 AM > > > > From: "Ryan Bloom" <[EMAIL PROTECTED]> > > Sent: Sunday, January 06, 2002 11:34 PM > > > > > 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. > > > > It allows us to have the following section; > > > > <Location /nowhere> > > DocumentRoot unset > > </Location> > > Oh... I forgot to point out the purpose in this. For an older > [incompletely ported] module, the syntax; > > <Location server-status> > SetHandler Status > DocumentRoot unset > </Location> > > gets rid of the stats that FirstBill complained of [which were in 1.3 as well.]
I was under the impression that those stats could be removed by having the status module implement a map-to-storage function. Did I misunderstand the purpose of that hook? I realize that putting the DocumentRoot directive in the core would allow a module author to not have to implement the map-to-storage hook and still receive the same benefit. I do not consider that a good reason to introduce the complexity of allowing DocumentRoot inside a <Location> container. Ryan ______________________________________________________________ Ryan Bloom [EMAIL PROTECTED] Covalent Technologies [EMAIL PROTECTED] --------------------------------------------------------------
