[dropping isapi_wsgi-dev because I'm not on it] On Mon, Dec 07, 2009, Preston Landers wrote: > > I'm running into a problem where it looks like threading is cropping > up again, even with the 'simple' WSGI base class. What I am looking > for is a way to completely shut off the possibility of multithreading, > as my app is not thread safe. I'm using multiple IIS worker processes > for concurrency. > > Most requests seem to be spaced out between different IIS worker > processes as desired. However in some cases with closely timed > requests I'm seeing two separate threads within the same process > handling the requests. I verified this with and without pydev > debugging extensions for Eclipse. One thread is labeled MainThread > and the other is Dummy-4 or something similar. It looks like the > Dummy label is created by threading.py _DummyThread. But I'm not > clear where the code is that's launching the thread, or for that > matter why it's choosing the 'dummy' implementation. The Python docs > suggest that 'alien' threads created through the C API would fall > under this category. This suggests that either the PyWin32 ISAPI C > code is launching the threads, or the ISAPI framework itself.
Do you have evidence that your Python code is running in multiple threads? I.e. are you sure this isn't just ISAPI running some cleanup work in another thread? -- Aahz (a...@pythoncraft.com) <*> http://www.pythoncraft.com/ The best way to get information on Usenet is not to ask a question, but to post the wrong information. _______________________________________________ python-win32 mailing list python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
