1. It takes care of packetization (as opposed to a regular TCP socket where one has to take care of assembling an entire message before feeding it to GBP)
2. Having a guaranteed 1 to 1 relationship helps on systems where multiple users can connect to your TCP ports. For eg. if I open a PUSH (tcp) socket, another user (by mistake or on purpose) can pull from the same queue and thus breaking my application functionality. 3. We've been using ZMQ + GBP in many places in our project, and because we now need p1 & p2, PAIR would be [almost] ideal. Otherwise we have to add a lot of extra-code to treat non-ZMQ communication separately. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Chuck Remes Sent: 18 January 2012 14:26 To: ZeroMQ development list Subject: Re: [zeromq-dev] ZMQ_PAIR sockets in 3.x ZMQ / IPC inwinows implementation On Jan 18, 2012, at 8:11 AM, Dorin Ciobanu (dciobanu) wrote: > ZMQ_PAIR - shame! They are very convenient when used in combination with > Google Proto-buffers. What is so useful about ZMQ_PAIR and google protocol buffers? Please explain your use-case; I'm certain we can suggest a superior replacement for ZMQ_PAIR that will also eliminate your occasional assertions. cr _______________________________________________ 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
