libuv/libuv

AF_UNIX on Windows

Open

#2,537 opened on Nov 10, 2019

View on GitHub
 (19 comments) (22 reactions) (0 assignees)C (3,870 forks)batch import
feature-requestgood first issuehelp wantedwindows

Repository metrics

Stars
 (26,843 stars)
PR merge metrics
 (Avg merge 54d) (12 merged PRs in 30d)

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?

  1. Since UV_NAMED_PIPE already means "named pipe" on Windows and "unix socket" on Unix, maybe a new UV_UNIX_SOCKET flag could be used to opt-into AF_UNIX behavior on Windows?
  2. Alternative: on Windows versions where AF_UNIX is supported, UV_NAMED_PIPE could use AF_UNIX unconditionally. But this could break applications that assume pipe names have \\.\pipe\... format.

Contributor guide

Research direction
Study the existing uv pipe * implementation on Windows and Unix, review the AF UNIX support in Windows 10 build 19041+, and propose a new UV UNIX SOCKET flag or adapt UV NAMED PIPE to use AF UNIX on supported Windows versions.
Tech stack
c
Domain
backendapi
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
CWindows API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50