We'll aim to solve this in the next release, yes.
On Wed, Nov 27, 2013 at 3:44 PM, 舒友村 <[email protected]> wrote: > Hi, > Thanks for your reply, would this bug 763 be resolved in next zeromq > version recently? > > > On Wed, Nov 27, 2013 at 8:54 PM, Pieter Hintjens <[email protected]> wrote: >> >> Hi, >> >> OK, I tested this across two machines, and you're absolutely right. >> When the router is running 2.2 and the dealer 4.0, there's an extra >> null message produced by the router. Here's a typical dump of messages >> the router delivers: >> >> -------------------------------------- >> [017] 00496C3B250C0042ABA57F226547411A77 >> [000] >> -------------------------------------- >> [017] 00496C3B250C0042ABA57F226547411A77 >> [006] 48656C6C6F00 >> >> The null message is sent when the dealer connects, even if it does not >> send any other message. I'm raising an issue, here: >> >> https://github.com/zeromq/libzmq/issues/763 >> >> -Pieter >> >> _______________________________________________ >> zeromq-dev mailing list >> [email protected] >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev > > > > > -- > > best！ > > > > 舒友村 > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
