Steps: - Pulled down the
Problems: - All the RemoteRequestServiceTestCase.cs tests fail, due to StubSocket not being castable to Socket - Tests "*when_recvTimeout_recv_should_return_null", "creating_pub" *and * "creating_sub_and_subscribing_to_specific_weird_topic"* all loop forever The culprit appears to be in https://github.com/castleproject/castlezmq/blob/master/src/Castle.Zmq/Socket.cs (The issue is in red): public byte[] Recv(bool noWait = false) { EnsureNotDisposed(); using (var frame = new MsgFrame()) { var flags = noWait ? Native.Socket.DONTWAIT : 0; again: // We loop here forever var res = Native.MsgFrame.zmq_msg_recv(frame._msgPtr, this.SocketPtr, flags); if (res == Native.ErrorCode) // It always is for the "looping" tests { var error = Native.LastError(); if (error == ZmqErrorCode.EAGAIN || error == ZmqErrorCode.EINTR) goto again; // It's always EAGAIN if (LogAdapter.LogEnabled) { LogAdapter.LogError("Socket", "Recv interrupted with " + error + " - " + Native.LastErrorString(error)); } Native.ThrowZmqError(error, "Recv"); } else { return frame.ToBytes(); } } return null; } Apart from the fact that these are failing, if you've set ZMQ noWait to be false, shouldn't *zmq_msg_recv* be blocking, rather than returning an instruction that you should block? This definitely looks like the best binding available for us, and I'm guessing you've solved these issues internally? Thanks for any help! PS. Also, watch out for Raptors <http://xkcd.com/292/>. -- You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to castle-project-users+unsubscr...@googlegroups.com. To post to this group, send email to castle-project-users@googlegroups.com. Visit this group at http://groups.google.com/group/castle-project-users. For more options, visit https://groups.google.com/d/optout.
