fixes #887 nn_send fails if issued immediately after nn_bind
Actually this just documents the asynchronous behavior of nn_connect/nn_bind.
diff --git a/doc/nn_bind.adoc b/doc/nn_bind.adoc
index 11e4de1..5203e95 100644
--- a/doc/nn_bind.adoc
+++ b/doc/nn_bind.adoc
@@ -32,6 +32,14 @@
on the same socket thus allowing the socket to communicate with multiple
heterogeneous endpoints.
+NOTE
+----
+
+Unlike with traditional BSD sockets, this function operates asynchronously,
+and returns to the caller before the operation is complete.
+As a result, attempts to send data or receive data on the socket may not
+succeed until the underlying transport actually establishes a connection.
+
RETURN VALUE
------------
If the function succeeds positive endpoint ID is returned. Endpoint ID can be
@@ -87,4 +95,5 @@
AUTHORS
-------
link:mailto:sustrik@250bpm.com[Martin Sustrik]
+link:mailto:garrett@damore.org[Garrett D'Amore]
diff --git a/doc/nn_connect.adoc b/doc/nn_connect.adoc
index 908d939..4c13881 100644
--- a/doc/nn_connect.adoc
+++ b/doc/nn_connect.adoc
@@ -32,6 +32,16 @@
on the same socket thus allowing the socket to communicate with multiple
heterogeneous endpoints.
+NOTE
+----
+
+Unlike with traditional BSD sockets, this function operates asynchronously,
+and returns to the caller before the operation is complete.
+As a result, attempts to send data or receive data on the socket may not
+succeed until the underlying transport actually establishes the connection.
+Further, the connection may be lost, without any notification to the caller.
+The library will attempt to reconnect automatically in such an event.
+
RETURN VALUE
------------
If the function succeeds positive endpoint ID is returned. Endpoint ID can be
@@ -83,4 +93,5 @@
AUTHORS
-------
link:mailto:sustrik@250bpm.com[Martin Sustrik]
+link:mailto:garrett@damore.org[Garrett D'Amore]
