Re: [whatwg/url] Addressing HTTP servers over Unix domain sockets (#577)

Just wanted to chime in here with my own opinion on this.

Unix domain sockets are an OS-specific transport. Windows does not have them, it has named pipes instead. Due to their local nature, simply embedding the Unix socket path or named pipe path would result in two different and somewhat incompatible representations for applications which must work on both Windows and Unix-like systems.

The ideal solution, would be to have some kind of alternative, ideally OS-neutral, namespace, perhaps under the IPv6 link-local or other reserved range, which maps directly to OS-specific network transports like Unix domain sockets or named pipes. For example, one could connect to `fe8f::3:6:0` port 12345, and it would map to a Unix socket at `/run/00006/00000_12345`. This may look weird at first, but the resulting path can still be symlinked to the actual socket to connect to. More generally, such a namespace and mapping could be configured by the user in a way such that an agreed-upon domain name or IP address could appear to connect to a local service, in a way that could be consistent across different operating systems, such that the agreed-upon domain name or IP address can be used to access the services in an OS-independent manner.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/issues/577#issuecomment-2381978110
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/url/issues/577/2381978110@github.com>