AF_UNIX on Windows
Open
Nobody has claimed this yet.
feature-request
good first issue
help wanted
windows
- Dominant language
- C
- Stars
- 27.2k
- Forks
- 3.9k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 17
Description
AF_UNIX is supported on Windows now, and has some advantages over named pipes:
https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/
What are your thoughts on adding support for this to the uv_pipe_* family of functions?
- Since
UV_NAMED_PIPEalready means "named pipe" on Windows and "unix socket" on Unix, maybe a newUV_UNIX_SOCKETflag could be used to opt-intoAF_UNIXbehavior on Windows? - Alternative: on Windows versions where
AF_UNIXis supported,UV_NAMED_PIPEcould useAF_UNIXunconditionally. But this could break applications that assume pipe names have\\.\pipe\...format.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the uv_pipe_* API behavior described in this issue and the linked Windows AF_UNIX announcement. Compare the proposed UV_UNIX_SOCKET option with changing UV_NAMED_PIPE, including compatibility with existing pipe-name expectations; the work is done when the API choice and Windows support behavior are specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100