durusmail: quixote-users: wsgi_server.py for Quixote
wsgi_server.py for Quixote
2005-04-29
2005-04-30
2005-04-30
2005-04-30
2005-04-30
2005-04-30
2005-04-30
2005-04-30
2005-04-30
2005-04-30
2005-04-30
2005-05-01
2005-05-01
2005-05-01
2005-05-02
2005-05-01
2005-05-01
2005-04-30
2005-04-30
2005-04-30
wsgi_server.py for Quixote
Titus Brown
2005-04-30
-> >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.

I'd suggest standardizing it by including it in Quixote proper as a
defined variable.  That way, other multithreaded servers (e.g. the
multithreaded SCGI server mentioned earlier by Ksenia) can use it
to be sure that they're supposed to be serving multithreaded Quixote
apps.

--titus
reply