httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Harrie Hazewinkel <har...@covalent.net>
Subject Re: [PATCH] mpm_query
Date Thu, 12 Apr 2001 08:48:09 GMT
rbb@covalent.net wrote:
[snip]
> >
> > Beyond that, there is nothing wrong with being informative :-)

I could not say it better.

> 
> My problem with the name, is that it requires chaning the API or adding a
> new API to deal with a string. 

Maybe this is some argument, but completely invalid. I interpret this
as I am lazy and don't want to do it. And how do you handle different
MPMs that have the same capabilities. Most likely with some name
provided by the MPM module you know more.

> I would prefer to not modify the API
> unless we need to now. 

Who determines the need?? I see a use and need for it. Does that count??
Or since I am not an hard-core Apache developper or ASF-member, it does
not
count??

> 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.

The server string gives way more information that needed here.

The problem is that since we do not standardise the capabilities
the 2 capabilites Ryan would add are not enough. In operational
environments it is mostly very usefull to know its name or
vendor of some piece of software, since it may have behavior
(for instance seg-faults) under certain conditions. This is indeed
the gray area, but for operators this is part of experience.
More like, ah, that machine we see this, which version does it have??
Ok, that happens more, we fix it this way.

Harrie
-- 
phone: +39-3474932300
http://www.lisanza.net/



Mime
View raw message