This won't work at the ZMTP level. CURVE must talk to CURVE. You could write a proxy that does raw TCP, and extends the CURVE handshake across from client to worker. You could also use libcurve on top of NULL, and do end-to-end security (that was the use case for libcurve).
On Fri, Nov 29, 2013 at 12:22 PM, Laurent Alebarde <[email protected]> wrote: > Hi all, > > Is it right to proxy CURVE ? I mean: > > CLIENT (CURVE) ------- (NULL) PROXY (NULL) ---------- (CURVE) WORKER > > I have identified a condition: the PROXY SHALL be ROUTER/ROUTER, and SHALL > maintain a table that assign on client always to the same worker for the > socket TTL. With this condition fullfilled, can you see some other > showstopper for such an architecture ? > > 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
