[doc] clarify absolute path format for unix URIs

pull/37913/head
Mark D. Roth 5 months ago
parent 1a422ebc29
commit 06c3372b14
  1. 8
      doc/naming.md

@ -34,12 +34,12 @@ Most gRPC implementations support the following URI schemes:
resolver does not support this, but the c-ares based resolver resolver does not support this, but the c-ares based resolver
supports specifying this in the form "IP:port".) supports specifying this in the form "IP:port".)
- `unix:path`, `unix://absolute_path` -- Unix domain sockets (Unix systems only) - `unix:path`, `unix:///absolute_path` -- Unix domain sockets (Unix systems only)
- `path` indicates the location of the desired socket. - `path` indicates the location of the desired socket.
- In the first form, the path may be relative or absolute; in the - In the first form, the path may be relative or absolute; in the
second form, the path must be absolute (i.e., there will actually be second form, the path must be absolute (i.e., the last of the three
three slashes, two prior to the path and another to begin the slashes is actually part of the path, so the path part of the URI is
absolute path). `/absolute_path`).
- `unix-abstract:abstract_path` -- Unix domain socket in abstract namespace (Unix systems only) - `unix-abstract:abstract_path` -- Unix domain socket in abstract namespace (Unix systems only)
- `abstract_path` indicates a name in the abstract namespace. - `abstract_path` indicates a name in the abstract namespace.

Loading…
Cancel
Save