[zeromq-dev] push/pull and multiple workers

andrea crotti andrea.crotti.0 at gmail.com
Fri Aug 17 15:17:23 CEST 2012

In that situation then you want to use a forwarder device. The forwarder
> device binds to an incoming and an outgoing port. The publisher(s) connect
> to the incoming port and the subscriber(s) connect to the outgoing port of
> the device.
> All messages flow through the device to the subscribers. By using the
> intermediate device, the subscribers do *not* need to know about every
> possible publisher. It's a very neat and tidy solution.
> cr
You mean something like this right? http://zguide.zeromq.org/py:wuproxy
looks very nice yes, but it brings me to another question, why do I have to
check for multipart
messages and handle them correctly even with default devices as the

Is there any case where it makes sense to not handle them maybe?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20120817/b5531d00/attachment.htm>

More information about the zeromq-dev mailing list