summaryrefslogtreecommitdiff
path: root/src/nng_compat.h
diff options
context:
space:
mode:
authorGarrett D'Amore <garrett@damore.org>2017-01-23 19:18:19 -0800
committerGarrett D'Amore <garrett@damore.org>2017-01-23 19:18:19 -0800
commit91a0b46b6a63f1c2345279b831a02c972e7b1781 (patch)
treee8dd692c29ee6ed2b5dd94897c97b3b9c9f690fc /src/nng_compat.h
parentfc553e0689a9be70b90663db1bcd020706ba9ae6 (diff)
downloadnng-91a0b46b6a63f1c2345279b831a02c972e7b1781.tar.gz
nng-91a0b46b6a63f1c2345279b831a02c972e7b1781.tar.bz2
nng-91a0b46b6a63f1c2345279b831a02c972e7b1781.zip
Add nn_sendmsg (with NN_MSG support).
Diffstat (limited to 'src/nng_compat.h')
-rw-r--r--src/nng_compat.h14
1 files changed, 14 insertions, 0 deletions
diff --git a/src/nng_compat.h b/src/nng_compat.h
index 0a147196..c49a33db 100644
--- a/src/nng_compat.h
+++ b/src/nng_compat.h
@@ -15,6 +15,20 @@
// and consumers should only use thse if they are porting software that
// previously used nanomsg. New programs should use the nng native APIs.
+// Note that compatibility promises are limited to public portions of the
+// nanomsg API, and specifically do NOT extend to the ABI. Furthermore,
+// there may be other limitations around less commonly used portions of the
+// API; for example only SP headers may be transported in control data for
+// messages, there is almost no compatibility offered for statistics.
+// Error values may differ from those returned by nanomsg as well; the nng
+// error reporting facility expresses only a subset of the possibilities of
+// nanomsg.
+
+// Note that unlinke nanomsg, nng does not aggressively recycle socket or
+// endpoint IDs, which means applications which made assumptions that these
+// would be relatively small integers (e.g. to use them as array indices)
+// may break. (No promise about values was ever made.)
+
#ifdef __cplusplus
extern "C" {
#endif