Linked by Thom Holwerda on Wed 20th Dec 2017 17:34 UTC
Windows

Support for the unix socket has existed both in BSD and Linux for the longest time, but, not on Windows. On Windows, there were some alternatives for local IPC, such as named pipes. But, calling conventions are different between the named pipes and sockets, making writing low-maintenance cross-platform applications difficult. For example, one such place where these two constructs differ (other than the API) is terminating the connection. BSD Socket API provides a bidirectional close semantics using 'shutdown'. There is no direct equivalent of that in named pipes. Such differences make it difficult to port unix socket applications from Linux to Windows and vice versa; up until now!

Build 17063 brings native support for the unix socket to Windows. Starting this build, two Win32 processes can use the AF_UNIX address family over Winsock API (which is very similar to the BSD socket API) to communicate with each other. Currently, the support only exists for the stream (SOCK_STREAM) socket type, which is a connection-oriented protocol for one-to-one communication. Support for the datagram (SOCK_DGRAM) can be considered in future depending on the adoption, feedback and scenarios.

Another step to make Windows friendlier to UNIX/Linux users and developers.

Permalink for comment 652260
To read all comments associated with this story, please click here.
Target Audience
by Alfman on Wed 20th Dec 2017 20:59 UTC
Alfman
Member since:
2011-01-28

Thom Holwerda,

Another step to make Windows friendlier to UNIX/Linux users and developers.



Call me a cynic, but I don't imagine microsoft really cared about unix sockets until it began affecting their internal development. In other words microsoft's developers responsible for porting and maintaining linux tools on windows were experiencing the frustrations of porting *nix software to windows.

I do wonder about the effectiveness of microsoft's strategy of supporting linux userspace on windows to regain the server market lost to linux. I know that I have zero interest in replacing linux with microsoft products. Anyone working for a company showing interest in this?

Edited 2017-12-20 21:01 UTC

Reply Score: 4