[ http://issues.apache.org/jira/brows...236
9996 ]

Jim Gallacher commented on MODPYTHON-145:
-----------------------------------------

Use of this PythonOption to configure apache in the unit tests interferes wi
th unit tests which are testing the PythonOption itself. These other tests a
ssume that PythonOption is only used in the testing of PythonOption, and wil
l need to be rewritten if w
e want to take advantage of PythonOption mod_python.mutex_locks or PythonOpt
ion mod_python.mutex_directory in the tests.

> Make number of mutex locks configurable at apache startup
> ---------------------------------------------------------
>
>          Key: MODPYTHON-145
>          URL: http://issues.apache.org/jira/browse/MODPYTHON-145
>      Project: mod_python
>         Type: New Feature
>   Components: core
>     Versions: 3.3
>     Reporter: Jim Gallacher
>     Assignee: Jim Gallacher
>     Priority: Minor

>
> The number of locks can already be specified at compile time usine ./confi
gure --with-max-locks=value
> For completeness, the maximum number of mutex locks created by python_init
 should be configurable via a PythonOption. The number of locks will only be
 set if the PythonOption directive appears in the server context. Any other 
context will be ignored.
> PythonOption mod_python.mutex_locks value
> The implementation of this will be similar to the code required for http://issue
s.apache.org/ji.../MODPYTHON-131.
> The number of locks can already be specified at compile time usine ./configure --w
ith-max-locks=value

[ Post a follow-up to this message ]