Hi all.
I've updated zmqHelper.hpp (https://github.com/cibercitizen1/zmqHelper)
two classes over zmq.hpp to make it easier tasks
like sending or receiving multipart (text) messages, polling sockets, etc;
and, in this version, to make sure that a socket cannot be shared
by different threads.
Hi,
(silent lurker on this list and no curve experience at all, but...)
"zeromq-dev" schrieb am 13.10.2016
08:59:15:
> I would like to swap the keys, so, the publisher should encrypt the data
> with his public key, and the subscribers should decrypt the data
Hi Roy,
it seems you are convoluting how ZeroMQ and CurveMQ work. ZMQ simply
abstracts how clients talk over a network. Pub-Sub is a fine example of
that since you, as a developer can write programs where clients can
fan-out messages, i.e. from one node to many others in one direction.
This does
On Thu, 2016-10-13 at 08:44 +, Auer, Jens wrote:
> Hi,
>
> will there be a ZeroMQ 4.1.6 release even if 4.2.0 is on the way? I have to
> fixes I'd like to be included. We are using a patched 4.1.5 and it would be
> great if 4.1.6 could include the two fixes:
> -
Hi,
will there be a ZeroMQ 4.1.6 release even if 4.2.0 is on the way? I have to
fixes I'd like to be included. We are using a patched 4.1.5 and it would be
great if 4.1.6 could include the two fixes:
- https://github.com/zeromq/libzmq/pull/1649/commits
-
Hello everyone,
Currently I'm investigating the possibilities of ZeroMQ.
At the moment, I have created a publisher subscribe system with curve enabled.
This is the code I used to get it up and running (got it from Pieter hintjes
his blog):
http://pastebin.com/LjV8aKLG
At the moment, the