Re: new directive (was Re: [patch] adding mpm info to httpd -V)

["William A. Rowe, Jr." <wr...@apache.org>]

At 02:10 PM 12/3/2003, Geoffrey Young wrote:

>>> <IfThreaded>
>>>     MaxThreadsPerChild   5
>>> </IfThreaded>
>> 
>> 
>> This rubs me the wrong way FWIW.  
>
>oops, sorry :)

I don't care for that container either... but even horrible new ideas 
are always good when then generate more ideas :)

>> If somebody really wants to do this they
>> could use IfDefine;  though it would be easier if the core pre-defined
>> some symbol for use in IfDefine, it is doable as-is.
>
>sure.  the only reason I didn't go that way was that the docs seem to say
>that <IfDefine> only applies to -D command-line parameters - I wasn't
>familiar enough with the directives to see if there were other, internal -D
>flags that were also used.

Actually, such defines might need to be a little more dynamic, but either
<IfDefine AP_MPM_THREADED> would be good, or if we absolutely
needed too, we could add <IfFeature FOO> where features could be
registered, by the core or by a loaded module.

Individual <IfFoo> blocks would pollute the command table significantly,
slowing down config parsing by a corresponding amount.

Bill

Re: new directive (was Re: [patch] adding mpm info to httpd -V)

[Geoffrey Young <ge...@modperlcookbook.org>]

William A. Rowe, Jr. wrote:
> At 02:10 PM 12/3/2003, Geoffrey Young wrote:
> 
> 
>>>><IfThreaded>
>>>>    MaxThreadsPerChild   5
>>>></IfThreaded>
>>>
>>>
>>>This rubs me the wrong way FWIW.  
>>
>>oops, sorry :)
> 
> 
> I don't care for that container either... but even horrible new ideas 
> are always good when then generate more ideas :)

:)

> 
> 
>>>If somebody really wants to do this they
>>>could use IfDefine;  though it would be easier if the core pre-defined
>>>some symbol for use in IfDefine, it is doable as-is.
>>
>>sure.  the only reason I didn't go that way was that the docs seem to say
>>that <IfDefine> only applies to -D command-line parameters - I wasn't
>>familiar enough with the directives to see if there were other, internal -D
>>flags that were also used.
> 
> 
> Actually, such defines might need to be a little more dynamic, but either
> <IfDefine AP_MPM_THREADED> would be good, or if we absolutely
> needed too, we could add <IfFeature FOO> where features could be
> registered, by the core or by a loaded module.

actually, the other idea I had (going for 0-2 on the horrible new idea theme
:) was <IfMPM AP_MPMQ_IS_THREADED> (or somesuch) as a direct interface to
ap_mpm_query, but I thought that outside of threaded/forked there wasn't
much other useful config-time information there.

but either/any form would probably be valuable to somebody somewhere along
the line.

> 
> Individual <IfFoo> blocks would pollute the command table significantly,
> slowing down config parsing by a corresponding amount.

ah, good point.

--Geoff

Re: new directive

[Geoffrey Young <ge...@modperlcookbook.org>]

> Actually, such defines might need to be a little more dynamic, but either
> <IfDefine AP_MPM_THREADED> would be good, or if we absolutely
> needed too, we could add <IfFeature FOO> where features could be
> registered, by the core or by a loaded module.

to that end, here's a preliminary and rough patch for

<IfServerIs !threaded>

(substitute 'IfServerIs' for whatever you please - I'm not so good with names).

I couldn't think of anything else to implement other than threadedness right
now, but I guess we're discussing the concept at the moment so that's ok.  I
did almost start on

<IfServerIs >= 2.1>

but I thought that the new container semantics probably wouldn't go over
well (and I wasn't entirely convinced that was a worthy thing to test at
config time).

--Geoff