> Hi, > Thanks for your suggestions. I used wsgiref to implement a bare-bones server > process. This is probably quite similar to the Flask dev server, but at least > it doesn't emit a big fat warning about not using in production, which would > make uninformed users uncomfortable. Since I'm running the server from the > restricted environment, cygwin is not an option here, so no uwsgi.
For the record, although Waitress starts a thread when you set it to threads = 1, I doubt it means that the thread-unsafe library in the app you're writing would have an issue. The main thread of any WSGI server would never be accessing any of the resources accessed by the library, so the threads it spawned would be the only point of contention, and since there's one, there is no contention. - C -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/pylons-discuss/zmiSu2oyjXA9TTGkRKyJxmejQvXFvCLxmumtsxrqvRJwj3PAXtJ02ckFDrX1eUdD8wdmZ0U9P5O5yoGcOAUCd2J_32E6K16PnMalSGxKZis%3D%40plope.com.
