On 13/11/2009 4:21 AM, Randy Syring wrote:
You may be able to use isapi-wsgi with a custom application pool to
achieve what you are looking for. If you can restrict the application
pool to only use one thread per process (which I am not sure how to do)
and then use multiple processes (properties
On 12/11/2009 10:03 AM, Preston Landers wrote:
4) Use isapi-wsgi: This seems to be getting more popular but it seems
to use threads and I'm wondering whether this will break my app in
subtle ways.
Thread support should be optional - it is if you use the lower-level
isapi stuff included in
On Thu, Nov 12, 2009 at 6:32 AM, Mark Hammond skippy.hamm...@gmail.com wrote:
On 12/11/2009 10:03 AM, Preston Landers wrote:
4) Use isapi-wsgi: This seems to be getting more popular but it seems
to use threads and I'm wondering whether this will break my app in
subtle ways.
Thread support
Preston Landers wrote:
On Thu, Nov 12, 2009 at 6:32 AM, Mark Hammond skippy.hamm...@gmail.com wrote:
On 12/11/2009 10:03 AM, Preston Landers wrote:
4) Use isapi-wsgi: This seems to be getting more popular but it seems
to use threads and I'm wondering whether this will break my app in
subtle
Preston Landers wrote:
4) Use isapi-wsgi: This seems to be getting more popular but it seems
to use threads and I'm wondering whether this will break my app in
subtle ways. I make heavy use of various Python C extension modules
which may not be fully threadsafe. Also within my app code there
Hello, all!
I'm a Python developer trying to get my web app working smoothly under
IIS on Windows - in particular with FastCGI though I am open to other
options. I posted on the IIS community forums about Python and
FastCGI but haven't heard a response there:
