feat(rs-transport): implement framed transport over TCP and UDS #364
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
rvolosatovs
changed the title
rvolosatovs
force-pushed
the
feat/transport-frame
branch
2 times, most recently
from
750e4c3 to
8127803
Compare
Signed-off-by: Roman Volosatovs <[email protected]>
rvolosatovs
force-pushed
the
feat/transport-frame
branch
from
8127803 to
a8b9b25
Compare
Signed-off-by: Roman Volosatovs <[email protected]>
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.
Implement a framed transport providing multiplexing to simple byte streams.
Include TCP and Unix socket implementations built on top of the same abstraction
Closes #9
windows named pipe supportI think this best belongs in a separate PR. TCP can already be used on all platforms