Support UDT transport protocol #3
Draft
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
amatissart
force-pushed
the
tokio-udt
branch
3 times, most recently
from
07daaaf to
a1d7fc1
Compare
amatissart
force-pushed
the
tokio-udt
branch
from
a1d7fc1 to
a79a201
Compare
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.
Now that the API for
tokio_udtis reasonably stable and the implementation seems to behave correctly, I implemented a PoC of how it could be integrated into talk, to use UDT as an optional replacement for the TCP protocol.TcpConnecttrait has been renamed intoConnectconnectmethod now acceptssettings: ConnectSettings, to choose between TCP and UDT, and possibly use a customUdtConfiguration.these
ConnectSettingscan be defined in rendezvousClientSettingsandServerSettings