[zeromq-dev] What is the exact issue with enabling MULTICAST_LOOP on ZMQ sockets?

[Steven McCoy]

On 11 June 2013 10:29, Chinmay Nerurkar <chinmay.nerurkar at fusionts.com>wrote:

> Thanks for the explanation. We need to have multiple publishers (publishing
> to one multicast channel) on the same host. As a follow-up to Marten's
> question, would the following design be an optimal solution to the problem?
>
> -A single ZMQ proxy process is started on a host with an incoming XSUB port
> bound to "ipc://inbound" and an outgoing XPUB port bound to one multicast
> channel "epgm://ethInterface;MulticastIP:MulticastPort".
> -All the publishing processes on the host connect to "ipc://inbound" on the
> proxy process and publish data.
> -The proxy publishes all received data to one multicast channel on its
> outbound port. This way there is only one multicast publisher per host.
>

Yes, this is a valid compromise.


> Also, just to make sure, is it possible to have multiple ZMQ EPGM XPUB
> sockets each bound to a different multicast channel, on the same/different
> Ethernet adapter on the same host?
>

Yes, it is recommended if you want to publish large or high data rate
content to split amongst multiple PGM streams.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20130611/d745ad89/attachment.htm>