You can change anything you like. Be clear about the semantics
however. The load balancing broker is sending requests for action to
workers. It's not a symmetric flow.
On Fri, Jan 9, 2015 at 6:24 AM, Kenneth Adam Miller
kennethadammil...@gmail.com wrote:
Can the mechanism of load balancing
I thought that the tidbits that were being received on the end of the
broker at the front end and backend (I'm talking about how in the guide it
refers to some of what is received as address and empty) were required
because of something to do with ZMQ internals-as though the address
received, and
Because, I was confused as to how Router sockets could continue an exchange
with a single REQ socket in a common context; I thought that they had to
obey some kind of semantics similar to REQ/REP-you send one and you recv
one... It just remembers who all connects to it?
On Fri, Jan 9, 2015 at
Can the mechanism of load balancing broker be changed so that exactly the
same send/recv pattern is followed regardless of which side connects?
On Thu, Jan 8, 2015 at 5:57 PM, Pieter Hintjens p...@imatix.com wrote:
In the lbbroker example all traffic flows through the broker.
On Thu, Jan 8,
Does the broker demonstrated in the manual under:
http://zguide.zeromq.org/page:all#A-Load-Balancing-Message-Broker
demonstrate that
A) when each end makes a connection request, after they link up from the
broker, their messages route directly between one another
In this scenario, the messages
