feat: add windows_named_pipe() option to client builder #2789
+313
−17
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
seanmonstar
force-pushed
the
windows-named-pipes
branch
6 times, most recently
from
7fdcc93 to
f647929
Compare
seanmonstar
force-pushed
the
windows-named-pipes
branch
from
f647929 to
6c7e217
Compare
seanmonstar
force-pushed
the
windows-named-pipes
branch
from
6c7e217 to
9d1e033
Compare
seanmonstar
force-pushed
the
windows-named-pipes
branch
from
9d1e033 to
bae129f
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.
Similar to adding support for Unix Domain Sockets in #2624, this adds support for Windows Named Pipes that functions the same way.
cc @danielsn @morrisonlevi