Windows IPC support

[raulk]

During devcon4 workshops, somebody suggested to use Named Pipes in Windows, as the Unix domain socket support is experimental. Suggested steps:

• Have somebody test the daemon as-is in Windows Insider Build 17063 or above, and report on results. Comment on this issue if you're up.
• Investigate https://github.com/Microsoft/go-winio, a Go wrapper for native Windows IO operations, maintained by Microsoft.
• Implement the changes to support this as a local transport for IPC.

[jrhea]

I'm curious...why not just use tcp instead of unix domain sockets?

[vyzo]

we are adding tcp support as well, as @bigs needs it for the testbed.
Main rationale is that unix domain sockets are faster and simpler, and also windows is adding support for AF_UNIX.

[jrhea]

@vyzo thanks for the info. I suppose there is always Cygwin for older versions of Windows. 👎

[bigs]

go-winio looks great. definitely something to add to the potential transport list.

[Nashatyrev]

May be better consider TCP option?
It looks like from the performance point of view on Windows TCP Loopback is faster than Named Pipes and approximately the same as new AF_UNIX.

Additionally:

• TCP option is cross-platform
• daemon can run on a remote machine which may be potentially interesting for some usage scenarios.

[vyzo]

this is already in progress -- see #41

[vyzo]

We have merged #41 so we can use localhost sockets on windows.