I find that a bit of an odd example. Doesn't the ability for a client
to asynchronously send lots of messages to a pool of workers imply the
need for message IDs? Otherwise the client doesn't know which message
a response is to. Yet that example doesn't make any attempt at
message IDs.
--
Best regards,
Jeremy Morton (Jez)
On 11/10/2016 23:14, joe meiring wrote:
check out the asynchronous request reply stuff in
http://zguide.zeromq.org/py:asyncsrv which uses all ROUTER/DEALER
sockets.
On Tue, Oct 11, 2016 at 4:56 PM, Jeremy Morton <[email protected]
<mailto:[email protected]>> wrote:
On 10/10/2016 10:24, Kevin Sapper wrote:
Hi Jeremy,
continue reading chapter 4
(http://zguide.zeromq.org/page:all#reliable-request-reply
<http://zguide.zeromq.org/page:all#reliable-request-reply>) which
should hold the solution!
I read it don't understand which part of chapter 4 you're
referring to which is pertinent to this situation - could you
enlighten me?
Fyi, when sending to a ROUTER socket zeromq attaches a sender ID
automatically. If you need to keep the order of messages
you'll need
to add message IDs yourself.
So does chapter 4 address this or not?
--
Best regards,
Jeremy Morton (Jez)
_______________________________________________
zeromq-dev mailing list
[email protected] <mailto:[email protected]>
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
<http://lists.zeromq.org/mailman/listinfo/zeromq-dev>
_______________________________________________
zeromq-dev mailing list
[email protected]
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
_______________________________________________
zeromq-dev mailing list
[email protected]
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
