Socket identity is going to be "prefixed" to the outgoing DEALER message. So, on ROUTER side there will be 3 parts.
2013/12/17 Pieter Hintjens <[email protected]> > Why is the ROUTER expecting 3 parts when the DEALER sends 2? > > On Tue, Dec 17, 2013 at 3:13 PM, artemv zmq <[email protected]> wrote: > > Ok. Got it. Here's pastebin snippet: http://pastebin.com/9fr8W0RA > > > > > > > > > > 2013/12/17 Pieter Hintjens <[email protected]> > >> > >> On Sat, Dec 14, 2013 at 6:47 PM, artemv zmq <[email protected]> > wrote: > >> > >> > There's no sense to paste code. Client is - DEALER. Server is ROUTER. > >> > Inside infinite loop client sends a message and await for reply. By > turn > >> > server -- inside infinite loop receives message and sends answer back. > >> > All > >> > socket settings -- by default. That's it. > >> > >> There are good reasons we make test cases for issues, and that the > >> wiki site says, "make a minimal test case". If it is trivial, please > >> post code. If it's not trivial, make it trivial, then please post > >> code. > >> > >> The group will otherwise ignore you (and rightly so). > >> > >> -Pieter > >> _______________________________________________ > >> 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 > > > _______________________________________________ > 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
