[zeromq-dev] ZMQ_STREAM interraction with ZMTP ?

Pieter Hintjens ph at imatix.com
Fri Dec 6 14:01:44 CET 2013

Please read my previous emails about proxying the CURVE handshake.
What I said still applies. The proxy has to parse the client's CURVE
commands and reply with valid CURVE commands. Using a STREAM socket it
can read the raw frames but then MUST pass them onto the worker, which
will generate the valid replies, which the proxy must then send back
to the client.

On Fri, Dec 6, 2013 at 12:59 PM, Laurent Alebarde <l.alebarde at free.fr> wrote:
> Hi Devs,
> I have connected a CURVE-DEALER socket with a ZMQ_STREAM one. Since
> ZMQ-STREAM is not a mechanism declared in stream_engine, I don't expect it
> creates any mechanism object.
> But, if I have not make mistakes, when the CURVE-DEALER socket sends its
> greeting, which includes "CURVE", then stream_engine creates an unexpected
> curve_client_t object. I assume this object is related to the ZMQ-STREAM
> socket since the options are the default ones, while I defined an identity
> to the CURVE-DEALER socket.
> On the other side, a "NULL" greeting is received, I assume onto the
> CURVE-DEALER socket from the ZMQ-STREAM socket, which is also not expected I
> think.
> test_stream.cpp passes but does it pass only because it is a NULL to STREAM
> communication ?
> If this is true, I think it is not a desirable behaviour.
> Are you aware of that ? Do you confirm ? What do you think about it ?
> Cheers,
> 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