From a35e8745f354e5569a4416869e755934fff717b4 Mon Sep 17 00:00:00 2001 From: gdamore Date: Thu, 9 Oct 2025 02:03:21 +0000 Subject: deploy: bdf85dd692d803b7b2fc793f1c7723f9874bfcdb --- ref/proto/push.html | 20 ++++++++++++++++---- 1 file changed, 16 insertions(+), 4 deletions(-) (limited to 'ref/proto/push.html') diff --git a/ref/proto/push.html b/ref/proto/push.html index 6f8aa876..f21f87f5 100644 --- a/ref/proto/push.html +++ b/ref/proto/push.html @@ -246,14 +246,14 @@

PUSH protocol

DESCRIPTION

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

+The other side is the PULL 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_push0_open call creates a PUSH socket. +

The nng_push0_open function creates a PUSH socket. This socket may be used to send messages, but is unable to receive them. Attempts to receive messages will result in NNG_ENOTSUP.

Send operations will observe flow control (back-pressure), so that @@ -269,14 +269,14 @@ wait until one is available, or the operation times out.

to avoid dropping messages, no guarantee of delivery is made. Furthermore, as there is no capability for message acknowledgment, applications that need reliable delivery are encouraged to consider the -REQ protocol instead.

+REQ protocol instead.

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