[zeromq-dev] Assertion failure in pull.cpp
sustrik at 250bpm.com
Sat Aug 21 19:02:18 CEST 2010
On 08/21/2010 03:21 PM, Pieter Hintjens wrote:
> On Sat, Aug 21, 2010 at 2:56 PM, Alexey Ermakov<zee at technocore.ru> wrote:
>> On Sat, Aug 21, 2010 at 1:57 PM, Pieter Hintjens<ph at imatix.com> wrote:
>>> Any other combinations e.g. XREP<->XREP or XREP<->XREQ must be bridged via code.
>> Wait a minute, XREQ<-> XREP aren't supposed to be connected to each
>> other? So the fact that it's possible and works right now is a bug?
> I don't know, and was over-hasty in writing that email.
> From a naive perspective XREQ and XREP have different representations
> for the message so aren't compatible. XREQ sends A and XREQ gives
They are compatible. The point is that you _want_ to see the identity on
the XREP side, although you haven't sent it on XREQ side.
> But that doesn't make it invalid, just undocumented.
> What is a bug (or at least a loophole) is allowing SUB<->SUB,
> PUB<->PUB, PUB<->PULL, XREQ<->PULL, etc.
More information about the zeromq-dev