[zeromq-dev] curve handcheck recovery behaviour ?

Pieter Hintjens ph at imatix.com
Thu Oct 3 12:10:51 CEST 2013

Hi Laurent,

Afaiu, EAGAIN is for internal retrying; EINTR is an interrupted
process, and EPROTO is an actual handshake error, which always leads
to the connection being broken. There's no handshake recovery process.


On Thu, Oct 3, 2013 at 12:03 PM, Laurent Alebarde <l.alebarde at free.fr> wrote:
> Hi Developpers,
> Could you please explain me how the curve handcheck behave when a bad packet
> is detected ? There are different types of errors : EPROTO, EINTR, EAGAIN,
> etc.. Some are fatal, others lead to a retry, others possibly to a abandon
> of the connexion.
> I understand for example that EAGAIN leads to a retry ? From the very
> beginning of the handcheck after having deleted or free all the objects like
> curve_server_t or mechanism_t ? Or only reset the current state and wait
> again for a valid message ? So isn't it more a WARNING ?
> A little description of the philosophy, behaviour and events would be very
> useful to me.
> Thanks in advance,
> Laurent.
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev

More information about the zeromq-dev mailing list