Support listen and connect via Unix Domain Sockets (UDS)

[eirnym]

Hello!

• Vote on this issue by adding a 👍 reaction
• If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

Support for Unix Domain Socket for listening and connection. Currently only TCP sockets are supported.

Why is this needed?

UDS solves following issues:

• Port pollution. When there's multiple ports opened, there's no human-readable information is attached to them so it's easy to find a situation when you have multiple ports and you have to guess what is what.
• Due to port pollution and human-readable names, it's easier to have star-domain config in servers like nginx e.g. *.example.com without ever changing it.
• UDS is faster because there's no TCP handshake before data is flowing
• Permission control via FS. On few systems like FreeBSD and macOS it's possible to set MAC to TCP ports, but it's impossible on Windows or Linux.
• UDS are well supported in all languages along with TCP.
• UDS on Windows works well, even it's implementation is different. I accept if it would be *BSD/Linux/macOS-specific at the beginning.