Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Windows named pipes #2079

Merged
merged 1 commit into from Sep 22, 2022
Merged

Support Windows named pipes #2079

merged 1 commit into from Sep 22, 2022

Conversation

lpinca
Copy link
Member

@lpinca lpinca commented Sep 21, 2022

Document how to connect to a named pipe endpoint and the limitations.

Refs: #1808
Refs: #2075

Document how to connect to a named pipe endpoint and the
limitations.

Refs: #1808
Refs: #2075
@lpinca lpinca changed the title [feature] Support Windows named pipes Support Windows named pipes Sep 21, 2022
@lpinca
Copy link
Member Author

lpinca commented Sep 21, 2022

cc: @hyurl @jacksteamdev

Copy link

@jacksteamdev jacksteamdev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lpinca Thanks for looking into this. Looks good to me.

I got this branch working in my POC; very exciting to get cross-OS support!

@lpinca lpinca merged commit ac7a005 into master Sep 22, 2022
@lpinca lpinca deleted the support/windows-named-pipes branch September 22, 2022 18:37
@lpinca
Copy link
Member Author

lpinca commented Sep 22, 2022

In the next major release it might make sense to rename the ws+unix: protocol to ws+ipc: for clarity/correctness.

lpinca added a commit that referenced this pull request Sep 22, 2022
Document how to connect to a named pipe endpoint and the limitations.

Refs: #1808
Refs: #2075
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants