[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 mult
On 12/12/2009 9:31 AM, Preston Landers wrote:
But I'm a little curious about the purpose of having a WSGI thread
pool implementation in light of those facts. If ISAPI will create
threads for you anyway, how does a pool help? Is it purely to avoid
thread startup overhead? If a thread is being c
On Mon, Dec 7, 2009 at 5:35 PM, Mark Hammond wrote:
> On 8/12/2009 9:45 AM, Preston Landers wrote:
>>
>> Someone had mentioned needing to restrict the worker pool to a single
>> thread but indicated they didn't know how to do that. I searched
>> around MSDN and couldn't find anything relevant. I
On 8/12/2009 9:45 AM, Preston Landers wrote:
Someone had mentioned needing to restrict the worker pool to a single
thread but indicated they didn't know how to do that. I searched
around MSDN and couldn't find anything relevant. I also checked the
PyWin32 ISAPI code and didn't see anything that
On Tue, Dec 1, 2009 at 5:33 AM, Mark Hammond wrote:
> On 1/12/2009 9:13 AM, Preston Landers wrote:
>>
>> I just thought I'd follow up on my original post about IIS. We
>> decided to go ahead and use isapi-wsgi and so far the results are very
>> good. It won't go into official production for a w
