The library may be configured with support for HTTP, and this will
diff --git a/man/tip/nng_http_client_connect.3http.html b/man/tip/nng_http_client_connect.3http.html
index 337b0d61..7054f4e3 100644
--- a/man/tip/nng_http_client_connect.3http.html
+++ b/man/tip/nng_http_client_connect.3http.html
@@ -578,7 +578,7 @@ obtained by
NNG_EADDRINVAL
diff --git a/man/tip/nng_listen.3.html b/man/tip/nng_listen.3.html
index 2a99e3cf..af26efdc 100644
--- a/man/tip/nng_listen.3.html
+++ b/man/tip/nng_listen.3.html
@@ -554,6 +554,9 @@ 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.
+
@@ -572,28 +575,6 @@ 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.
-
-
-
-
-|
-
- |
-
-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 nng_listener_create() and
diff --git a/man/tip/nng_listener_start.3.html b/man/tip/nng_listener_start.3.html
index 63e02fd6..7934a2b0 100644
--- a/man/tip/nng_listener_start.3.html
+++ b/man/tip/nng_listener_start.3.html
@@ -551,27 +551,7 @@ Each new connection results in an nng_pipe
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.
-
-
-
-
-|
-
- |
-
-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
diff --git a/man/tip/nng_options.5.html b/man/tip/nng_options.5.html
index 3a100634..6d9c46a2 100644
--- a/man/tip/nng_options.5.html
+++ b/man/tip/nng_options.5.html
@@ -567,25 +567,28 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
retrieved on objects in the nng library.
+
+
Other object types may have additional methods to access these options.
In addition to the options listed here, transports and protocols will generally
@@ -607,11 +610,28 @@ description of the option.
NNG_OPT_LOCADDR
-
-
(nng_sockaddr)
+
(nng_sockaddr)
This read-only option may be used on listeners, dialers and connected pipes, and
-represents the local address used for communication.
-Not all transports support this option, and some transports may support it
-listeners but not dialers.
+represents the local address used for communication.
+
+
+
+|
+
+ |
+
+Not all transports support this option, and some transports may support it on
+listeners but not dialers.
+ |
+
+
+
+
+
When used on a TCP dialer, this option is used to configure the source IP
+address that will be used when initiating outgoing connections.
+The specific port number will be ignored, however, and the system will
+choose a random ephemeral port instead.
+
@@ -624,13 +644,15 @@ listeners but not dialers.
(bool)
This read-only option indicates whether the socket is in “raw” mode.
If true, the socket is in “raw” mode, and if false the socket is
-in “cooked” mode.
-Raw mode sockets generally do not have any protocol-specific semantics applied
+in “cooked” mode.
+
+
Raw mode sockets generally do not have any protocol-specific semantics applied
to them; instead the application is expected to perform such semantics itself.
(For example, in “cooked” mode a rep socket would
automatically copy message headers from a received message to the corresponding
reply, whereas in “raw” mode this is not done.)
See Raw Mode for more details.
+
@@ -639,7 +661,7 @@ See Raw Mode for more details.
NNG_OPT_RECONNMINT
-(nng_duration)
+(nng_duration)
This is the minimum amount of time (milliseconds) to wait before attempting
to establish a connection after a previous attempt has failed.
This can be set on a socket, but it can also be overridden on an individual
@@ -654,7 +676,7 @@ The option is irrelevant for listeners.
-(nng_duration)
+(nng_duration)
This is the maximum amount of time
(milliseconds) to wait before attempting to establish a connection after
a previous attempt has failed.
@@ -702,9 +724,6 @@ This descriptor will be readable when a message is available fo
on the socket.
When no message is ready for receiving, then this file descriptor will not
be readable.
-
-
-
@@ -728,11 +747,14 @@ returned file descriptor.
While this option may help applications integrate into existing polling
loops, it is more efficient, and often easier, to use the asynchronous I/O
objects instead.
-See nng_aio_alloc().
+See nng_aio_alloc().
+
+
+
NNG_OPT_RECVMAXSZ
@@ -748,9 +770,6 @@ where a malicious agent can claim to want to send an extraordinarily
large message, without sending any data.
This option can be set for the socket, but may be overridden for on a
per-dialer or per-listener basis.
-
-
-
@@ -758,18 +777,21 @@ per-dialer or per-listener basis.
|
-Some transports may have further message size restrictions!
+Some transports may have further message size restrictions.
|
+
+
+
NNG_OPT_RECVTIMEO
-
-(nng_duration)
+(nng_duration)
This is the socket receive timeout in milliseconds.
When no message is available for receiving at the socket for this period of
time, receive operations will fail with a return value of NNG_ETIMEDOUT.
@@ -780,7 +802,7 @@ time, receive operations will fail with a return value of NNG_ETIMEDOUT
NNG_OPT_REMADDR
-
-
(nng_sockaddr)
+
(nng_sockaddr)
This read-only option may be used on dialers and connected pipes, and
represents the address of a remote peer.
Not all transports support this option.
@@ -798,9 +820,6 @@ This is the depth of the socket send buffer as a number of messages.
Messages sent by an application may be buffered by the socket until a
transport is ready to accept them for delivery.
This value must be an integer between 0 and 8192, inclusive.
-
-
-
@@ -815,6 +834,9 @@ simply discard messages when they cannot be delivered immediately.
+
+
+
NNG_OPT_SENDFD
@@ -829,13 +851,12 @@ for use with
select(),
(or on Windows systems
WSAPoll())
-and similar functions.
-This descriptor will be readable when the socket is able to accept a
+and similar functions.
+
+
This descriptor will be readable when the socket is able to accept a
message for sending without blocking.
When the socket is no longer able to accept such messages without blocking,
the descriptor will not be readable.
-
-
@@ -845,7 +866,7 @@ the descriptor will not be readable.
|
Applications should never attempt to read or write to the
-returned file descriptor.
+returned file descriptor; use should be limited to polling system calls only.
|
@@ -860,18 +881,21 @@ returned file descriptor.
While this option may help applications integrate into existing polling
loops, it is more efficient, and often easier, to use the asynchronous I/O
objects instead.
-See
nng_aio_alloc().
+See
nng_aio_alloc().