From 45ac4fa56b6e5c31a28fd08eaad14a09bf3934f6 Mon Sep 17 00:00:00 2001 From: gdamore Date: Sun, 27 Oct 2024 18:55:51 +0000 Subject: deploy: ffeb31c64ea72c4eb287f75b641ca2a707df90b0 --- ref/proto/pull.html | 322 ++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 322 insertions(+) create mode 100644 ref/proto/pull.html (limited to 'ref/proto/pull.html') diff --git a/ref/proto/pull.html b/ref/proto/pull.html new file mode 100644 index 00000000..64b65dcf --- /dev/null +++ b/ref/proto/pull.html @@ -0,0 +1,322 @@ + + + + + + PULL Protocol - NNG Reference Manual (DRAFT) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ + + + + + + + + + + + + + + + + + + +
+ +
+ + + + + + + + +
+
+ +

PULL protocol

+

The PULL protocol is one half of a +pipeline pattern. +The other half is the PUSH protocol.

+

In the pipeline pattern, pushers distribute messages to pullers. +Each message sent +by a pusher will be sent to one of its peer pullers, +chosen in a round-robin fashion +from the set of connected peers available for receiving. +This property makes this pattern useful in load-balancing scenarios.

+

Socket Operations

+

The nng_pull0_open functions create a +PULL socket. +This socket may be used to receive messages, but is unable to send them. +Attempts to send messages will result in NNG_ENOTSUP.

+

When receiving messages, the PULL protocol accepts messages as +they arrive from peers. +If two peers both have a message ready, the +order in which messages are handled is undefined.

+

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 PULL protocol has no protocol-specific options.

+

Protocol Headers

+

The PULL protocol has no protocol-specific headers.

+ +
+ + +
+
+ + + +
+ + + + + + + + + + + + + + + + + + + +
+ + -- cgit v1.2.3-70-g09d2