From b1bdec4404047db7cf2356555c8f8749c2865b2b Mon Sep 17 00:00:00 2001 From: Ilya Kulakov Date: Mon, 10 Aug 2015 22:32:16 -0400 Subject: [PATCH] Fix documentation of the ZMQ_REQ_CORRELATE option. Full message is actually (request id, identity, 0, user frames...). --- doc/zmq_setsockopt.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/zmq_setsockopt.txt b/doc/zmq_setsockopt.txt index 0025ef5f..5dec1869 100644 --- a/doc/zmq_setsockopt.txt +++ b/doc/zmq_setsockopt.txt @@ -533,7 +533,7 @@ ZMQ_REQ_CORRELATE: match replies with requests The default behavior of REQ sockets is to rely on the ordering of messages to match requests and responses and that is usually sufficient. When this option is set to 1, the REQ socket will prefix outgoing messages with an extra frame -containing a request id. That means the full message is (request id, 0, +containing a request id. That means the full message is (request id, identity, 0, user frames...). The REQ socket will discard all incoming messages that don't begin with these two frames.