[zeromq-dev] Calling connect more than once on the same endpoint

Pieter Hintjens ph at imatix.com
Wed Oct 16 16:39:36 CEST 2013


Having said that, it is undocumented behavior, and there is no valid
use for this in pub-sub (nor in dealer-router, nor in req-rep) and we
might want to change the behavior. We do know what endpoints are
already used, and could reject duplicate connects to the same
endpoint.

On Wed, Oct 16, 2013 at 4:26 PM, Pieter Hintjens <ph at imatix.com> wrote:
> Yes, this is expected behavior. Each connect is independent. In
> pub-sub this produces nonsense results but in other patterns it can be
> used to do things like prioritize one node over others (e.g. a PULL
> that connects twice to a PUSH).
>
> On Wed, Oct 16, 2013 at 4:17 PM, Trevor Bernard
> <trevor.bernard at gmail.com> wrote:
>> I have a PUB/SUB topology and I accidently called connect twice to the
>> same PUB endpoint and received duplicate messages. This holds true for
>> N connects as well. Is this the correct behaviour?
>>
>> Simple test that recreates it:
>>
>>     https://github.com/trevorbernard/double-trouble/blob/master/src/double_trouble/core.clj
>>
>> -Trev
>> _______________________________________________
>> zeromq-dev mailing list
>> zeromq-dev at lists.zeromq.org
>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
>
>
> --
> -
> Pieter Hintjens
> CEO of iMatix.com
> Founder of ZeroMQ community
> blog: http://hintjens.com



-- 
-
Pieter Hintjens
CEO of iMatix.com
Founder of ZeroMQ community
blog: http://hintjens.com



More information about the zeromq-dev mailing list