You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In .NET Core 2.1, we've added a public EndPoint-derived type for Unix domain sockets (UnixDomainSocketEndPoint). Unix domain sockets work across all Unixes we target, but Windows is also adding support (https://blogs.msdn.microsoft.com/commandline/2017/12/19/af_unix-comes-to-windows/), and we can support that via UnixDomainSocketEndPoint as well. We should consider adding:
Some version of Windows 10 supports Unix domain sockets; having a capability API to check this without having to know the exact OS version
Only concern is that there are more capability APIs we might have to expose in the future. It's debatable whether a Boolean properties on this type are the correct pattern, but it seems consistent with prior art and domain sockets are reasonably common.
namespace System.Net.Sockets
{publicpartialclassSocket{publicstaticboolOSSupportsUnixDomainSockets{get;}// Existing APIs// public static bool OSSupportsIPv4 { get; }// public static bool OSSupportsIPv6 { get; }}}
System.Net.Socket
currently has these two properties:In .NET Core 2.1, we've added a public EndPoint-derived type for Unix domain sockets (UnixDomainSocketEndPoint). Unix domain sockets work across all Unixes we target, but Windows is also adding support (https://blogs.msdn.microsoft.com/commandline/2017/12/19/af_unix-comes-to-windows/), and we can support that via UnixDomainSocketEndPoint as well. We should consider adding:
The text was updated successfully, but these errors were encountered: