Skip to content
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

Improve guidance for threads in Connexion V3 #1986

Open
chrisinmtown opened this issue Oct 29, 2024 · 0 comments
Open

Improve guidance for threads in Connexion V3 #1986

chrisinmtown opened this issue Oct 29, 2024 · 0 comments

Comments

@chrisinmtown
Copy link

Description

Please provide much more information about workers and threads in the new V3. The getting started document advises:

You can still use workers as before, however you should not use threads with ASGI, since it handles concurrency using an async event loop instead.

One of my applications spawns a thread at startup which performs various tasks periodically. Some requests that are sent to Flask by the OpenAPI layer are passed to that thread via a thread-safe queue with appropriate locking etc. No requests result in the code spawning a new thread to handle the request.

Expected behaviour

Documentation explains exactly what thread operations are safe, and which are dangerous.

Actual behaviour

Documentation is vague.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant