i am getting a “send frame error” from SendMessage.
is there anyway to get more information on what is going on?
i tried sticking in a perror right after the C.zframe_send (in sock.go) but
(apparently) errno had been set (or overwritten) to some unknown error.
andrew
On Mon, 2016-11-07 at 11:37 +0100, Peter Kleiweg wrote:
> Peter Kleiweg schreef op de 7e dag van de slachtmaand van het jaar 2016:
>
> >
> > Of the new socket options mentioned in the release notes for
> > ZeroMQ 4.2, the options ZMQ_SOCKS_PROXY and ZMQ_BLOCKY are not
> > documented in either
On Mon, 2016-11-07 at 09:16 +0100, Peter Kleiweg wrote:
> The release notes for ZMQ 4.2 mentions the new function
> zmq_curve_public. This function is undocumented. Is it save to
> use it anyway?
Yes it should be added to the doc, fair point.
It is safe and the implementation uses, as
Peter Kleiweg schreef op de 7e dag van de slachtmaand van het jaar 2016:
>
> Of the new socket options mentioned in the release notes for
> ZeroMQ 4.2, the options ZMQ_SOCKS_PROXY and ZMQ_BLOCKY are not
> documented in either zmq-getsockopt or zmq-setsockopt.
>
> Should I ignore these?
>
>
Of the new socket options mentioned in the release notes for
ZeroMQ 4.2, the options ZMQ_SOCKS_PROXY and ZMQ_BLOCKY are not
documented in either zmq-getsockopt or zmq-setsockopt.
Should I ignore these?
(I'm updating Go bindings zmq4 for version 4.2)
--
Peter Kleiweg
The release notes for ZMQ 4.2 mentions the new function
zmq_curve_public. This function is undocumented. Is it save to
use it anyway?
--
Peter Kleiweg
http://pkleiweg.home.xs4all.nl/
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
