From 02e90dd4f29037e43f28e3bd1e912d4092011d23 Mon Sep 17 00:00:00 2001 From: Garrett D'Amore Date: Fri, 28 Dec 2018 21:49:05 -0800 Subject: fixes #833 nng_listener_listen and nng_listen ignore the flags fixes #829 nn_dial function annotation in nng.h --- docs/man/nng_listen.3.adoc | 13 ++----------- docs/man/nng_listener_start.3.adoc | 12 +----------- 2 files changed, 3 insertions(+), 22 deletions(-) (limited to 'docs') diff --git a/docs/man/nng_listen.3.adoc b/docs/man/nng_listen.3.adoc index 41d1fa9f..e569da4f 100644 --- a/docs/man/nng_listen.3.adoc +++ b/docs/man/nng_listen.3.adoc @@ -36,6 +36,8 @@ An incoming connection generally results in and Unlike dialers, listeners generally can create many pipes, which may be open concurrently. +The _flags_ argument is ignored, but reserved for future use. + TIP: While it is convenient to think of listeners as "`servers`", the relationship between the listener or dialer is orthogonal to any server or client status that might be associated with a given protocol. @@ -43,17 +45,6 @@ For example, a <> socket might have associated dialers, but might also have associated listeners. It may even have some of each at the same time! -Normally, the act of "`binding`" to the address indicated by _url_ is done -synchronously, including any necessary name resolution. -As a result, a failure, such as if the address is already in use, will be -returned immediately. -However, if the special value `NNG_FLAG_NONBLOCK` is supplied in _flags_, -then this is done asynchronously; furthermore any -failure to bind will be periodically reattempted in the background. - -TIP: While `NNG_FLAG_NONBLOCK` can help an application be more resilient, -it also generally makes diagnosing failures somewhat more difficult. - Because the listener is started immediately, it is generally not possible to apply extra configuration; if that is needed applications should consider using `<>` and diff --git a/docs/man/nng_listener_start.3.adoc b/docs/man/nng_listener_start.3.adoc index 852a859a..4703c9ca 100644 --- a/docs/man/nng_listener_start.3.adoc +++ b/docs/man/nng_listener_start.3.adoc @@ -32,17 +32,7 @@ dialers. Each new connection results in an `<>` object, which will be attached to the listener's socket. -Normally, the act of "`binding`" to its address is done -synchronously, including any necessary name resolution. -As a result, -a failure, such as if the address is already in use, will be returned -immediately. -However, if the special value `NNG_FLAG_NONBLOCK` is -supplied in _flags_, then this is done asynchronously; furthermore any -failure to bind will be periodically reattempted in the background. - -TIP: While `NNG_FLAG_NONBLOCK` can help an application be more resilient, -it also generally makes diagnosing failures somewhat more difficult. +The _flags_ argument is ignored, but reserved for future use. Once a listener has started, it is generally not possible to change its configuration. -- cgit v1.2.3-70-g09d2