From 331bd5a7c360083f245fe6c82afa38dd05c4a9c9 Mon Sep 17 00:00:00 2001 From: Garrett D'Amore Date: Sun, 24 Mar 2024 22:19:42 -0700 Subject: More org stuff --- docs/reference/src/protocols/pub.md | 40 +++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 docs/reference/src/protocols/pub.md (limited to 'docs/reference/src/protocols/pub.md') diff --git a/docs/reference/src/protocols/pub.md b/docs/reference/src/protocols/pub.md new file mode 100644 index 00000000..bd49b1d3 --- /dev/null +++ b/docs/reference/src/protocols/pub.md @@ -0,0 +1,40 @@ +# PUB Protocol + +The {{i:_PUB_ protocol}}{{hi:protocol, _PUB_} is one half of a {{i: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_](sub.md) protocol is the subscriber side. + +> [!NOTE] +> 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. + +## Socket Operations + +The [`nng_pub0_open()`](../api/nng_pub_open.md) 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 `NNG_ENOTSUP`. + +## Protocol Versions + +Only version 0 of this protocol is supported. +(At the time of writing, no other versions of this protocol have been defined.) + +## Protocol Options + +The _PUB_ protocol has no protocol-specific options. + +## Protocol Headers + +The _PUB_ protocol has no protocol-specific headers. -- cgit v1.2.3-70-g09d2