torsdagen den 16 februari 2006 22.48 skrev Jim Gallacher:
Oden Eriksson wrote:
tisdagen den 14 februari 2006 13.17 skrev Oden Eriksson:
Hello.
[...]
I am no programmer, but can't you just look at how this is handled in the
core mod_ssl and ldap code?
That would be cheating and no
Jim Gallacher wrote ..
If the settings are going to be a generic key/value like in
PythonOption, but only for purposes of the mod_python system itself,
maybe it should be called PythonSystemOption. Prefer PythonSystemOption
as Module is too confusing to me given you have both Apache
Jim Gallacher wrote ..
I have a better option (pun intended). :-)
We do not need a new directive. Instead use existing PythonOption
directive.
That could work.
In the handler code for the directive, it can look at the
value of the cmd_parms-path and determine if it is being used
Graham Dumpleton wrote ..
Graham Dumpleton wrote ..
How does req.server.get_options() differ from req.server.get_config(),
which already exists?
I still see what is in get_config() as special, ie., the values for
actual directives. Just don't think it is good to mix them.
Looking
Hello.
In our package in Mandriva I patch mod_python.c so that the mutex stuff is put
in /var/cache/httpd/mod_python/. But now with mod_python-3.2.7 plus fixes
from the trunk and running the test suite it complains it cannot access
/var/cache/httpd/mod_python/ (of course). So my
On Tue, 14 Feb 2006, Jim Gallacher wrote:
I wonder if we should generalize this, so rather than PythonMutexDir, we have
PythonModuleConfig. Usage might look like:
PythonModuleConfig mutex_dir /path/to/mutexs
PythonModuleConfig max_mutex_locks 8
I may be wrong, but I think the reason this
