|This documentation is for the TIP (development tree) of NNG and may represent unreleased changes or functionality that is experimental, and is subject to change before release. The latest released version is v1.3.2. See the documentation for v1.3.2 for the most up-to-date information.|
nng_pub - publisher protocol
(protocol, pub) The 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 pub protocol is the publisher side, and the sub 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.
nng_pub0_open() functions create a publisher socket.
This socket may be used to send messages, but is unable to receive them.
Attempts to receive messages will result in
Only version 0 of this protocol is supported. (At the time of writing, no other versions of this protocol have been defined.)
The pub protocol has no protocol-specific options.
The pub protocol has no protocol-specific headers.