It seems that the cause is the use of ZMQ_STREAM with inproc ?
Le 08/02/2014 09:16, Laurent Alebarde a écrit :
Hi Devs,
I assume I have done something wrong, but I don't know what. Does
somebody has an idea what can cause such failure please ?
The context is a poll of three sockets:
void
Any idea when clrzmq binding will be updated to support zmq4?
Thanks
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Hi Devs,
The doc says: /CURVE is intended for use on public networks./, but it
does not say it does not work on other transport than tcp. Thought,
following the debugger, it appears that it is not activated with the
inproc transport. Moreover, the stream_engine where protocol
negotiations
ZMTP is a TCP-based protocol. CURVE assumes tcp:// as the transport.
There's no valid use case for CURVE security between threads in one process.
Over ipc:// conceivably, it could make sense.
On Sun, Feb 9, 2014 at 10:41 AM, Laurent Alebarde l.aleba...@free.fr wrote:
Hi Devs,
The doc says:
Thanks for the clarification Pieter.
In my need to proxy CURVE, the idea was to have inproc at both CURVE
end-points, before stacking the protocols. Stacking the protocols would
have been more efficient with inproc.
I do:
Client DEALER -- STREAM -- DEALER wild TCP ROUTER -- STREAM
Hello developers,
I downloaded and compiled zmq3 (3.2.5). Running make check
found 1 not-passed test. As per output, I report the log here.
I am running debian stable (i386).
Regards
-F
Making check in src
make[1]: Entering directory `/home/f-a/media/vcs/zeromq3-x/src'
make[1]: Leaving
