[zeromq-dev] Understanding Broker

[Kenneth Adam Miller]

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 11:55 AM, Kenneth Adam Miller <
kennethadammiller at gmail.com> wrote:

> 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 then sent with SNDMORE was being used to help route it, and
> because it was a router socket, you would *have* to receive that part.
>
> But this is strange, because on the other end, there is just a send and
> recv; it's really simple. Do you mean to say that the address message
> received on one end *doesn't* have to do with ZMQ internals as I assumed,
> and that the backend and frontend routing logic can be duplicated on each
> end, so long as frontend requests and frontend handlers are pairwise
> consistent (and likewise to backend)?
>
> On Fri, Jan 9, 2015 at 4:45 AM, Pieter Hintjens <ph at imatix.com> wrote:
>
>> 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
>> <kennethadammiller at gmail.com> wrote:
>> > 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 <ph at imatix.com> wrote:
>> >>
>> >> In the lbbroker example all traffic flows through the broker.
>> >>
>> >> On Thu, Jan 8, 2015 at 8:39 PM, Kenneth Adam Miller
>> >> <kennethadammiller at gmail.com> wrote:
>> >> > 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 sent by each side on request will hit
>> the
>> >> > broker, but the replies they send will go directly to one another.
>> >> >
>> >> > or
>> >> >
>> >> > B) that at all times, information is routing via the broker?
>> >> >
>> >> > In this scenario, the requests have to first go to the broker, and
>> then
>> >> > the
>> >> > replies also hit the broker, which it ferries across to each side.
>> >> >
>> >> > Which is the case?
>> >> >
>> >> > _______________________________________________
>> >> > zeromq-dev mailing list
>> >> > zeromq-dev at lists.zeromq.org
>> >> > http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>> >> >
>> >> _______________________________________________
>> >> zeromq-dev mailing list
>> >> zeromq-dev at lists.zeromq.org
>> >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>> >
>> >
>> >
>> > _______________________________________________
>> > zeromq-dev mailing list
>> > zeromq-dev at lists.zeromq.org
>> > http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>> >
>> _______________________________________________
>> zeromq-dev mailing list
>> zeromq-dev at lists.zeromq.org
>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20150109/360142d6/attachment.htm>