#include <nng/nng.h>
-int nng_close(int s);close a socket
close all open sockets
close socket
create and start a dialer
create and start dialer
get a socket option
get socket option
create and start a listener
create and start listener
set a socket option
set socket option
The following functions are used with either listeners, or dialers. +Listeners accept incoming connection requets, and dialers make them.
+| + | create and start dialer |
+
| + | close dialer |
+
| + | create dialer |
+
| + | get dialer option |
+
| + | set dialer option |
+
| + | start dialer |
+
| + | create and start listener |
+
| + | close listener |
+
| + | create listener |
+
| + | get listener option |
+
| + | set listener option |
+
| + | start listener |
nng_close - close a socket
+nng_close - close socket
#include <nng/nng.h>
-int nng_close(int s);The nng_close() function closes the supplied socket, 's'. Messages
+
The nng_close() function closes the supplied socket, s. Messages
that have been submitted for sending may be flushed or delivered,
depending upon the transport and the setting of the NNG_OPT_LINGER
option.
NNG_EBADF result.
NNG_EBADFThe socket is already closed or was never opened.
+The socket s is already closed or was never opened.
nng_dial - create and start dialer
+#include <nng/nng.h>
+
+int nng_dial(nng_socket s, const char *url, nng_dialer *dp, int flags);The nng_dialer() function creates a newly initialized
+dialer, associated with socket s, and configured to listen at the
+address specified by url. If the value of dp is not NULL, then
+the newly created dialer is stored at the address indicated by dp.
Dialers initiate a remote connection to a listener. Upon a successful +connection being established, they create a pipe, add it to the socket, +and then wait for that pipe to be closed. When the pipe is closed, +they will re-initiate the connection. Dialer’s will also periodically +retry a connection automatically if an attempt to connect asynchronously +fails.
+| + + | ++While it is convenient to think of dialers as "clients", the relationship +between the listener or dialer is orthogonal to any server or client status +that might be associated with a given protocol. For example, a REQ +socket might have associated dialers, but might also have associated listeners. +It may even have some of each at the same time! + | +
Normally, the first attempt to connect to the address indicated by url is done +synchronously, including any necessary name resolution. As a result, +a failure, such as if the connection is refused, will be returned +immediately, and no further action will be taken.
+However, if the special value NNG_FLAG_NONBLOCK is
+supplied in flags, then the connection attempt is made asynchronously.
Furthermore, if the connection was closed for a synchronously dialed +connection, the dialer will still attempt to redial asynchronously.
+| + + | +
+While NNG_FLAG_NONBLOCK can help an application be more resilient,
+it also generally makes diagnosing failures somewhat more difficult.
+ |
+
Because the dialer is started immediately, it is generally not possible +to apply extra configuration; if that is needed applications should consider +using nng_dialer_create(3) and +nng_dialer_start(3) instead.
+This function returns 0 on success, and non-zero otherwise.
+NNG_EADDRINVALAn invalid url was specified.
+NNG_ECLOSEDThe socket s is not open.
+NNG_ECONNREFUSEDThe remote peer refused the connection.
+NNG_ECONNRESETThe remote peer reset the connection.
+NNG_EINVALAn invalid set of flags was specified.
+NNG_ENOMEMInsufficient memory is available.
+NNG_EPEERAUTHAuthentication or authorization failure.
+NNG_EPROTOA protocol error occurred.
+NNG_EUNREACHABLEThe remote address is not reachable.
+Copyright 2018 Staysail Systems, Inc.
+Copyright 2018 Capitar IT Group BV
+
+This document is supplied under the terms of the MIT License.