David Binger wrote:

> On Apr 30, 2005, at 4:43 PM, Titus Brown wrote:
>
>> My suspicion is that the Quixote developers mainly work with SCGI (as do
>> I, these days) and don't want to have to test thread-safety.  I
>
>
> That's true.
>
>> For the nonce, why not have QWIP check wsgi.multithreaded and raise an
>> exception if it's true, and then if Quixote gets retrofitted to provide
>> thread-safety info we can have it rely on that?
>
>
> QWIP might also look to the publisher class
> for an attribute (or a superclass)  that asserts thread safety.


That's what I was thinking of.

if (env['wsgi.multithreaded'] and not
    getattr(self.publisher, 'is_thread_safe', False)):
    raise RuntimeError("this Quixote publisher is not thread safe")

That way legacy publishers are assumed unsafe but new publishers can
assert their status, without QWIP imposing particular superclass
requirements.  If David is OK with the attribute name, I can put it in
wsgi_server.py now and he can add it to Publisher later.