OK, now it works. Pieter, are you interested in having this test :
* just as a full libzmq alternative to the czmq one in the Guide. How
do I add it ?
* As an additional test to libzmq ? Even if by design it is proved to
work.
* Just a pastbin link here <http://pastebin.com/pmY2vWMr> ?
The rationale for me at the beginning of this work is to test security
mechanisms (like CURVE) under multithreading.
At first glance, I have to keep the same worker for the same client, and
maintain a table in the broker. Your insights are welcome.
If you look at the code, you will see a variant of zmq_proxy with an
additional socket argument that adds flow control to the proxy with
STOP/RESUME/TERMINATE commands. This argument has defaults to NULL, then
it is fully backward compatible. I can pull request that if you which.
Le 15/10/2013 15:37, Laurent Alebarde a écrit :
Thanks Pieter, I was sure there was an obvious reason, but I did not
catch this one.
Le 15/10/2013 15:35, Pieter Hintjens a écrit :
On Tue, Oct 15, 2013 at 3:27 PM, Laurent Alebarde<[email protected]> wrote:
So, can you see any obvious reason why this does not work please ?
You're creating separate contexts for client and server and then
trying to use inproc across those. That won't work.
You can pass the context to child threads so they can use it instead
of creating their own.
-Pieter
_______________________________________________
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
