aboutsummaryrefslogtreecommitdiff
path: root/docs/man/nng_ipc.7.adoc
diff options
context:
space:
mode:
Diffstat (limited to 'docs/man/nng_ipc.7.adoc')
-rw-r--r--docs/man/nng_ipc.7.adoc5
1 files changed, 4 insertions, 1 deletions
diff --git a/docs/man/nng_ipc.7.adoc b/docs/man/nng_ipc.7.adoc
index 199aa757..5a73ce25 100644
--- a/docs/man/nng_ipc.7.adoc
+++ b/docs/man/nng_ipc.7.adoc
@@ -42,7 +42,7 @@ no extra steps to use it should be necessary.
(((URI, `ipc://`)))
This transport uses URIs using the scheme `ipc://`, followed by
-a an absolute path name in the file system where the socket or named pipe
+an absolute path name in the file system where the socket or named pipe
should be created.
TIP: On Windows, all names are prefixed by `\\.\pipe\` and do not
@@ -56,6 +56,9 @@ then pathnames must not be longer than 122 bytes, including the final
This is because legacy versions of _nanomsg_ cannot express URLs
longer than 128 bytes, including the `ipc://` prefix.
+NOTE: Legacy _nanomsg_ supported relative IPC path names; modern _nng_ does not.
+Therefore, always use an absolute path name if interoperability is required.
+
=== Socket Address
When using an <<nng_sockaddr.5#,`nng_sockaddr`>> structure,