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 --
DEALER Worker
CURVE NULL NULL CURVE
But the STREAM socket needs also tcp apparently.
Le 09/02/2014 20:24, Pieter Hintjens a écrit :
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 <[email protected]> wrote:
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 are handchecked is
not parsed. So shall I assume that with inproc, ZMTP at all is not used ?
What should be patched to activate it on a socket bases whatever is the
transport, via a setsocketoption ?
Cheers,
Laurent
_______________________________________________
zeromq-dev mailing list
[email protected]
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
_______________________________________________
zeromq-dev mailing list
[email protected]
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
_______________________________________________
zeromq-dev mailing list
[email protected]
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
