From 122bd6086c0fef009f582d6c4fec5a5a3ae5e6de Mon Sep 17 00:00:00 2001 From: Garrett D'Amore Date: Wed, 28 Mar 2018 10:19:46 -0700 Subject: Include a tip about service naming guidelines. --- docs/man/nng.7.adoc | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/man/nng.7.adoc b/docs/man/nng.7.adoc index 7b145a54..ee120774 100644 --- a/docs/man/nng.7.adoc +++ b/docs/man/nng.7.adoc @@ -146,6 +146,13 @@ Note that steps 4, 5, and 7 are not specified by RFC 3986, but performing them is believed to improve both the usability and security of _nng_ applications, without violating RFC 3986 itself. +TIP: Port numbers may be service names in some instances, but it is recommended +that numeric port numbers be used when known. +If service names are used, it is recommended that they follow the naming +conventions for C identifiers, and not be longer than 32 characters in length. +This will maximize compatibility across systems and minimize opportunities for +confusion when they are parsed on different systems. + == API The library API is documented at <>. -- cgit v1.2.3-70-g09d2