[ http://issues.apache.org/jira/browse/MODPYTHON-191?page=all ]
Graham Dumpleton resolved MODPYTHON-191.
Resolution: Fixed
Tampering with signed cookies.
--
Key: MODPYTHON-191
URL:
[ http://issues.apache.org/jira/browse/MODPYTHON-195?page=all ]
Graham Dumpleton updated MODPYTHON-195:
---
Fix Version/s: 3.3
Possible leaking of Win32 event handles when Apache restarted.
[
http://issues.apache.org/jira/browse/MODPYTHON-195?page=comments#action_12447742
]
Graham Dumpleton commented on MODPYTHON-195:
Can you see if you can come up with some check based on values of 'initialized'
and
On 04/11/2006, at 12:34 PM, Jeff Robbins wrote:
Graham,
I haven't had any new ideas about this problem. It is clear that
on Windows, mod_python is initialized both in a parent process and
more usefully in the child process that spins up the threads that
service client requests. The
Graham,
The problem on Win32 is that (I believe) we never want to initialize Python
in the persistent parent process. All the web action is in the child
process which is long-lived and it is this child process that maintains the
thread pool which services web requests.
The parent process
Graham,
The problem on Win32 is that (I believe) we never want to initialize Python
in the persistent parent process. All the web action is in the child
process which is long-lived and it is this child process that maintains the
thread pool which services web requests.
The parent process
