-
-
Notifications
You must be signed in to change notification settings - Fork 754
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document how to allow long running request not block everything else #62
Comments
Yes, not specifying the server will run Flask with the Werkzeug development HTTP server --- which is not meant for production usage. You can either run Connexion with gevent, Tornado or some WSGI container (not tested, see #54). |
I'm reopening this issue as the mentioned behavior (gevent monkey patch, uWSGI, etc) is not yet fully documented (in README or connexion.readthedocs.org). |
This is not really an issue of Connexion, but we should make it easy for people without prior Python/Flask/WSGI knowledge 😄 |
Does it covers what is expected by this issue? |
Closing this issue, we have info about that in the |
This makes sense for the gevent lib, since the corresponding libraries are patched. How does this work with something like tornado, where we must yield a Future object? |
Now per default the long running request is blocking all other requests. This is an issue of Flask, but still would make sense to document.
Here is an example from Henning's email:
The text was updated successfully, but these errors were encountered: