[MODPYTHON-202] Allow mechanism used by global mutex locks to be specified.

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.2.10
• Component/s: core
• Assignee: Unassigned
• Reporter: Graham Phillip Dumpleton
• Created: 08/Nov/06 22:41
• Updated: 08/May/07 10:39

Description

When using experimental Apache ITK MPM, described at:

http://home.samfundet.no/~sesse/mpm-itk/

global mutex locks will fail if Apache used semaphores because requests against different virtual hosts run as different users and user will not have permission to access the semaphore to lock it. See:

http://www.modpython.org/pipermail/mod_python/2006-November/022536.html

for original mailing list post about this from Sam Morris.

A suggested fix of finding a specific mechanism that works rather than default used by Apache, seems to work:

http://www.modpython.org/pipermail/mod_python/2006-November/022537.html
http://www.modpython.org/pipermail/mod_python/2006-November/022538.html
http://www.modpython.org/pipermail/mod_python/2006-November/022539.html

If available MPMs with such constraints are going to appear, may make sense to have an option to configure which allows one to override at compile time the default mechanism used for global mutex locks so that it can be made to match what may be required for a specific MPM that Apache is compiled to use.