|Unix sockets come to Windows|
|By Thom Holwerda on 2017-12-20 17:34:05|
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.
- The PowerPC 600 series and Windows NT - 2018-08-07
- Windows NT and VMS: the rest of the story - 2018-07-31
- Microsoft to improve Windows update experience - 2018-07-25
- Windows command-line: inside the Windows console - 2018-07-23
- More related articles