It's impossible to receive a message twice, since we use TCP unicast for messages.
As Arnaud says, UDP may send the same message twice. However zbeacon sends on a single interface, so that isn't possible either. On Fri, Nov 7, 2014 at 2:22 PM, Arnaud Loonstra <arn...@sphaero.org> wrote: > On 11/07/2014 02:13 PM, Joss Gray wrote: >> Currently ZRE messages are not uniquely identifiable ( AFAIK ) so if you >> receive the same message multiple times, particularly when there are >> multiple network adapters, you can't tell if the same message was sent 3 >> times, or received 3 times. >> >> Particularly SHOUT and WHISPER messages. You cant receive more than 1 >> valid JOIN messages for a peer in a row without a LEAVE. >> >> I'd like to suggest adding a UUID to the ZRE spec, then add filtering of >> duplicate messages into zyre. >> > > The messages are counted to prevent duplicate messages. > > I.e.: > https://github.com/zeromq/zyre/blob/master/src/zyre_node.c#L659 > > Although that method just checks for lost messages... > > What can happen is receiving broadcast beacons twice in case zbeacon > listens and sends on all interfaces. > > Rg, > > Arnaud > -- > w: http://www.sphaero.org > t: http://twitter.com/sphaero > g: http://github.com/sphaero > i: freenode: sphaero_z25 > _______________________________________________ > zeromq-dev mailing list > zeromq-dev@lists.zeromq.org > http://lists.zeromq.org/mailman/listinfo/zeromq-dev _______________________________________________ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
