![\"ZeroMQ\"](\"http:\/\/bobbeaty.com\/wp\/wp-content\/uploads\/2010\/07\/ZeroMQ.gif\" "\\"ZeroMQ.gif\\"")
<\/p>\n<\/p>\n
It really breaks my heart to see problems with ZeroMQ<\/a> that aren't being addressed. For instance, I've been trying to work with the guys on IRC about the fact that the GitHub master doesn't receive messages when using OpenPGM<\/a>. I've talked to the guys on IRC about this, and it seems that some of the more recent changes really messed this up, and there were no checks on the code to make sure it was still working. Sad, but true.<\/p>\n I've tried several times to jump-start this several times, but I didn't get very far on any occasion. This makes it hard to use, as I can't use it without OpenPGM<\/a>, but I'd like to get some of the newer features they are talking about.<\/p>\n But that's not the worst.<\/p>\n I think ZeroMQ<\/a> is either delaying, re-ordering, or retrying with excessive<\/em> delay, some of my messages - and it's only when I'm really hammering the data rate. For example, I know that the ZeroMQ<\/a> send()<\/tt> method is asynchronous<\/em>. So it buffers up the data and then sends it. But what if it gets messed up?<\/p>\n The delivery seems to get worse and worse as the day goes on, and it seems<\/em> to be based on a zmq::socket_r<\/tt> getting into a \"bad state\" and never getting itself out. I believe<\/em> that it's in the receiver, because two apps on the same box have different reception profiles after a time.<\/p>\n