On 2 December 2010 13:23, Steven McCoy <steven.mc...@miru.hk> wrote:
> to_write 100 // message #1 payload
>
>
Ok, imagine the numbers were actually incrementing.
Looks like a concurrency issue. If I add the following simple trace the
issue disappears,
bool zmq::encoder_t::message_ready ()
{
// Destroy content of the old message.
zmq_msg_close (&in_progress);
// Read new message. If there is none, return false.
// Note that new state is set only if write is successful. That way
// unsuccessful write will cause retry on the next state machine
// invocation.
if (!source || !source->read (&in_progress)) {
zmq_msg_init (&in_progress);
*puts ("no new message");*
return false;
}
--
Steve-o
_______________________________________________
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
