[zeromq-dev] epgm: PUB and SUB sockets on same host cant communicate

Michael Haberler mail17 at mah.priv.at
Mon Sep 10 18:30:30 CEST 2012

Am 10.09.2012 um 17:51 schrieb Steven McCoy:

> On 10 September 2012 10:26, Michael Haberler <mail17 at mah.priv.at> wrote:
> I have epgm publisher & subscriber working just fine - as long as they run on different hosts
> both on the same host with say 'epgm://eth0;' are unable to communicate, regardless of using bind() or connect() on the subscriber side
> is this a known restriction? any workarounds? didnt find any hints in TFM

> Yes, a design decision for 3.x.  The workaround is to simply add an IPC endpoint to the socket for local apps.  You can hard hack the support back in too, it's just a socket option on the underlying PGM socket.

re workaround: the application I had in mind was to synchronize state across several hosts with a scheme where both talker and listener would operate on the same epgm URI; for that the IPC workaround doesnt help, it means one UDP port per host, and more setup hassle

anyway, good to know

thanks for the explanation!

- Michael

> I plan to implement a slower more flexible multicast transport that supports such paradigms, another popular request is atomic multicast.  Unfortunately no ETA or early access for a while, subject to available research time.
> -- 
> Steve-o
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev

More information about the zeromq-dev mailing list