On Thu, 12 Apr 2001, Harrie Hazewinkel wrote:
> Hi all,
>
> I have made a new patch for the mpm_query functionality.
>
> 1) This patch extends the information that can be retrieved.
> 2) It also allows to return an MPM_TYPE which is a string.
> This is used to provide some additional information
> about the MPM used. It even could be used by an MPM
> developper to provide an arbitrary human readable
> string which can be used for management purposes.
-1 for returning the string from this function. It makes the function
harder to read and to use. If you absolutely must have a way to query the
MPM name, then use a separate function for it. Something like
ap_show_mpm() like Sander suggested yesterday.
> 3) The AP_MPMQ_IS_FORKED and AP_MPMQ_ISTHREADED now return
> a capability. It now can return 3 values:
> - NOT_SUPPORTED = 0
> - STATIC = 1
> - DYNAMIC = 2
> This mechanism is to enable other module to figure
> out the capabilities for threading and forking.
> If one wants to have the same results as previous
> (which was not more then a true/false) you can
> consider value 0 (not supported) as false and
> static and dyniamc true.
> There is actually no need to make even a capabilities
> value besides the IS_FORKED and IS_THREADED.
I like this section. I'll commit it today if I have the time to rip out
the string handling.
Ryan
_______________________________________________________________________________
Ryan Bloom [EMAIL PROTECTED]
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------
