On Wed, 11 Apr 2001, William A. Rowe, Jr. wrote:
> From: <[EMAIL PROTECTED]>
> Sent: Wednesday, April 11, 2001 12:39 PM
>
>
> > On Wed, 11 Apr 2001, Sander van Zoest wrote:
> >
> > > The more accurate information you have in the noc the better. Why monitor
> > > if you do not know what you are monitoring?
> >
> > The problem is that the MPM name is not accurate. We have a habit of
> > changing names of things. The MPM properties are the best way to
> > determine the behavior of the MPM IMNSHO.
>
> 100% correct that we need to test features (dynamically), not the arbitrary
> name of some MPM.
>
> Beyond that, there is nothing wrong with being informative :-)
My problem with the name, is that it requires chaning the API or adding a
new API to deal with a string. I would prefer to not modify the API
unless we need to now. Not that I am dead-set against changing the API, I
just want a good reason before we do so. I don't believe that allowing
modules to query the name of the MPM is a good reason. IMHO, the correct
way for somebody to get the name of the MPM, is to use the ServerString.
Ryan
_______________________________________________________________________________
Ryan Bloom [EMAIL PROTECTED]
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------
