Socket addresses are intended to provide a concise way to describe the “address” of network socket.
The original use case was to provide a simple way to describe listening sockets in a uniform way.
For a command line interface there should only be a single --socket=<address> parameter,
regardless of whether the specified address is IPv4 or IPv6 – or even a Unix Domain Socket path.
While similarly looking, socket addresses neither are URIs nor to be considered a part/subset of them.
For example, in comparison to URIs there’s no protocol scheme or path.
Also there are no domain names in socket addresses (thus no DNS resolution necessary or provided).
Parsing of all kind of socket addresses
Currently supported
Rules
Idea
Socket addresses are intended to provide a concise way to describe the “address” of network socket.
The original use case was to provide a simple way to describe listening sockets in a uniform way. For a command line interface there should only be a single --socket=<address> parameter, regardless of whether the specified address is IPv4 or IPv6 – or even a Unix Domain Socket path.
Relation to URIs
While similarly looking, socket addresses neither are URIs nor to be considered a part/subset of them.
For example, in comparison to URIs there’s no protocol scheme or path. Also there are no domain names in socket addresses (thus no DNS resolution necessary or provided).