QUIC FUTURE: Add concurrency architecture design document #24256
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
hlandau
added
branch: master
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 is not for the QUIC Server MVP. It is a design document produced as part of some necessary long term planning for API evolution to support high performance multithreaded I/O in advanced server applications.
As such, it is not a review priority. However, comment and feedback is of course welcomed.
However, the first part of this document introduces relevant concepts which will be used in the QUIC Server MVP in PRs to follow as this is necessary to fix #24166. You can stop reading at the heading "Architecture" if you don't care about the future stuff and only want to know about 3.4-relevant things.
The potential architecture for a Concurrency Management Layer (which enables both WCM and non-WCM concurrency models to be implemented without having to maintain two radically different code paths) discussed here is a first draft under contemplation and might change substantially further down the line. It is intended as a preview of some internal architectural designs which are being considered.