On Apr 30, 2005, at 6:05 PM, Mike Orr wrote:

> 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.

That sounds fine to me.  We can add the attribute if you want it.

If you intend for this to work with earlier versions of the quixote
Publisher, though, are you convinced that there is a benefit of
having "is_thread_safe = False" on the quixote publisher class?
It seems like any python code should be assumed to be
not-thread-safe at least until someone studies it and describes
the conditions under which it may be treated as thread-safe.