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 for AF_UNIX on Windows #1320

Open
gdamore opened this issue Nov 1, 2020 · 0 comments
Open

Support for AF_UNIX on Windows #1320

gdamore opened this issue Nov 1, 2020 · 0 comments

Comments

@gdamore
Copy link
Contributor

gdamore commented Nov 1, 2020

Windows 10 now supports AF_UNIX. While we currently support named pipes, AF_UNIX has some distinct advantages, and so we should consider supporting it:

  1. It is possible to use AF_UNIX to communicate with WSL processes on the same machine.
  2. AF_UNIX preserves the UNIX semantics of binding and cleaning up the process, which could resolve an ongoing complaint.
  3. AF_UNIX supports abstract sockets on both Windows and Linux

There are drawbacks as well:

  • There is probably already an installed base of named pipe users
  • Named pipes give us access to the security descriptor -- AF_UNIX probably won't

Long term it seems like AF_UNIX is going to be the way to go. What we'll probably do is add a unix: style URL, and maybe also an "mspipe:" URL. I imagine that in NNG 2.0 we would make ipc change from being mspipe to using AF_UNIX. In some further off future we would probably deprecate (remove) the mspipe URL altogether.

@gdamore gdamore added this to the v1.4 milestone Nov 1, 2020
@gdamore gdamore modified the milestones: v1.4, v1.5 Dec 29, 2020
@gdamore gdamore modified the milestones: v1.5, v1.8 Jan 2, 2024
@gdamore gdamore modified the milestones: v1.8, v2.0 Jan 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant