[zeromq-dev] changing the C++ api to not throw exceptions on EFSM

[Yi Ding]

On Wed, Jan 25, 2012 at 5:09 PM, Martin Sustrik <sustrik at 250bpm.com> wrote:

> Hi Yi,
>
>
>  However, if we use REQ/REP in conjunction with ZMQ_FD, as we currently
>> do in our code and nzmqt (I'm sure it's also used in other bindings)
>> EFSM is basically unavoidable as triggering a EFSM is required if we
>> want to "reset" the receive state for the edge-triggering.
>>
>
> Can you explain the scenario?
>
> Martin
>

Basically right now we have to call zmq_recv repeatedly until we get a
EAGAIN, otherwise the edge-triggered file descriptor won't reset.  The
problem is that calling zmq_recv on a rep or req socket can also return a
EFSM, which will trigger an exception in the C++ interface, which we then
have to catch and handle.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20120125/3a075efd/attachment.htm>