Mike Orr wrote:

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