Rework transport and internal implementation to support multiplexed transports #255
Conversation
This file contains hidden or 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
Test Results 825 files 825 suites 46m 11s ⏱️ For more details on these failures, see this check. Results for commit 0834fbc. ♻️ This comment has been updated with latest results. |
whyoleg force-pushed the rework-transport branch 2 times, most recently from 87696ca to c71adfb Compare 
…ransports * new Transport API * migrate local to new Transport API and introduce multiplexed kind * fix some tests to use port 0 to auto-assign port
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
1 participant
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.
io.rsocket.kotlin.transport)Note:
Motivation:
To support QUIC and other possible multiplexed transports, native support for streams on transport level is needed.
But internal implementation was not ready for this. Additionally, it was a good idea to fix some issues with inconsistent transport API and hard to maintain internals.