-> >If the flag exists, implementors of safe publishers will override it.
->
-> Of course, the Publisher might be thread-safe and the application not.
-> But I'm not sure that's our responsibility, or what to do if it is.
-> There could be an .is_thread_safe on the top-level Directory, but I'm
-> not sure that's the best way to go about it.  We certainly shouldn't
-> recursively check all Directories because some might not be Directories
-> at all and others might be undiscoverable by normal means.  I think in
-> terms of the application writer being the sysadmin himself and thus
-> knowing what kind of WSGI components are appropriate for it.  But that
-> wouldn't be the case for a sysadmin deploying a third-party
-> application.  I guess the create_publisher function has the ultimate
-> knowledge, so it should set publisher.is_thread_safe = False if it knows
-> the Publisher is safe but the application is not.

Don't most people subclass the Publisher themselves?  I haven't done
much Quixote 2.0 development, but in Quixote 1.2 and before the default
Publisher was pretty minimal.  Making a new Publisher was usually my
1st or 2nd item on a new project.

As for thread safety, I'd prefer to lay ambiguity to rest, so setting
is_thread_safe to *something* is good.  As-is, Quixote is pretty easy
to *make* thread-safe, so I have no opinion on whether or not it should
be thread-safe out of the box.  My suspicion is that the lowest common
denominator (== not thread safe) is the smart way to go, but YMMV.

cheers,
--titus