Add stronger wording on the relationship between lifespans, event loops, threads and processes #338
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ps, threads and processes.
andrewgodwin
approved these changes
Jul 24, 2022
adriangb
changed the title
|
Thank you, Andrew! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This tweaks the wording on the relationship between lifespans, event loops, threads and processes.
I believe this is not introducing anything new, the intention is already there in the spec, it's just not very strongly worded/clear.
All of the server implementations that are currently in widespread use and support lifespans (Hypercorn and Uvicorn; Daphne does not support lifespans) comply with this, so this will not break/conflict with any implementations.