#include <nng/nng.h>
-int
-nng_close (int s);The nng library is wire compatible with the SP protocols described in -the nanomsg project; projects using libnanomsg can interoperate with +the nanomsg project; projects using libnanomsg can inter-operate with nng as well as other conforming implementations. (One such implementation is the mangos. Applications using nng which wish to communicate with older libraries must ensure that they only @@ -492,19 +492,31 @@ other languages please check the website.
nng_bus(7) - Bus protocol
+nng_bus(7) - Bus protocol
nng_pair(7) - Pair protocol
+nng_pair(7) - Pair protocol
nng_pubsub(7) - Publish/Subscribe protocol
+nng_pub(7) - Publisher side of publish/subscribe protocol
nng_reqrep(7) - Request/Reply protocol
+nng_sub(7) - Subscriber side of publish/subscribe protocol
nng_survey(7) - Survey/Respond protocol
+nng_rep(7) - Reply side of request/reply protocol
+nng_req(7) - Request side of request/reply protocol
+nng_respondent(7) - Respondent side of survey protocol
+nng_surveyor(7) - Surveyor side of survey protocol
+nng_surveyor(7) - Survey/Respond protocol
#include <nng/nng.h>
-int
-nng_close (int s);#include <nng/transport/inproc/inproc.h>
-int
-nng_inproc_register(void);The sa_family member will have the value NNG_AF_INPROC (1).
-The sa_path member is an ASCIIZ string, and may contain any charaters,
+The sa_path member is an ASCIIZ string, and may contain any characters,
terminated by a NUL byte.
nng_pub - publisher protocol
+#include <nng/protocol/pubsub/pubsub.h>
+
+#define NNG_PROTO_PUB_V0 32
+#define NNG_PROTO_PUB NNG_PROTO_PUB_V0
+
+int nng_pub_open(nng_socket *s);
+int nng_pub0_open (nng_socket *s);The nng_pub protocol is one half of a publisher/subscriber pattern. +In this pattern, a publisher sends data, which is broadcast to all +subscribers. The subscribing applications only see the data to which +they have subscribed.
+The nng_pub protocol is the publisher side, and the +nng_sub(7) protocol is the subscriber side.
+| + + | ++In this implementation, the publisher delivers all messages to all +subscribers. The subscribers maintain their own subscriptions, and filter +them locally. Thus, this pattern should not be used in an attempt to +reduce bandwidth consumption. + | +
The topics that subscribers subscribe to is just the first part of +the message body. Applications should construct their messages +accordingly.
+The nng_pub_open() call creates a publisher socket. This socket
+may be used to send messages, but is unable to receive them. Attempts
+to receive messages will result in NNG_ENOTSUP.
Only version 0 of this protocol is supported. (At the time of writing, +no other versions of this protocol have been defined.)
+The nng_pub protocol has no protocol-specific options.
+The nng_pub protocol has no protocol-specific headers.
+Copyright 2017 Garrett D’Amore
+Copyright 2017 Capitar IT Group BV
This document is supplied under the terms of the +MIT License.
+