Hi Jerry,
It looks like you're forgetting to subscribe on the client end. The
publisher won't send anything because the client never told it that it
wanted to subscribe. You can just subscribe to "" to get all messages.
Cheers,
Aaron
On 1 March 2016 at 19:18, Jerry Scharf
wrote:
> Hi,
>
> I
Hi,
I have req/rep working fine now. There is one deviation from the pyzmq
documentation. The documentation says that you use socket.send with a
string, but the code errors out and says use send_string instead. I
don't know if this is a version problem in the zmq I built, but I just
did pip in
Well, the main issue with depending on libsodium is that in certain
environments (anything needing Cmake) the hassle of building it is so
large that people either don't use ZeroMQ, or use it without security.
The tweetnacl code is much smaller and simpler than libsodium. I don't
think it's accurat
On Tue, Mar 01, 2016 at 07:45:38PM +0100, Roland Fehrenbacher wrote:
> Thanks for this clarification. So does everybody agree on the following:
>
> - Use the included tweetnacl for build/compile convenience
> - Use libsodium for clean distribution type of builds
> - Technically, both variants are
I have developed an experimental wrapper for the excellent ZMQ4 golang binding
at
https://github.com/pebbe/zmq4
The wrapper allows for zmq.Socket to be wrapped so they can be accessed
through golang channels in a threadsafe and idiomatic manner. This allows
(inter-alia) golang select statements
On 1 March 2016 at 18:45, Roland Fehrenbacher wrote:
>> "F" == frank writes:
>
> F> On 03/01/2016 02:51 PM, Roland Fehrenbacher wrote:
> >>> "P" == Pieter Hintjens writes:
> P> Frank, Thanks for your opinion. You hit it spot on, I think. It
> P> is really a relief to hav
> "F" == frank writes:
F> On 03/01/2016 02:51 PM, Roland Fehrenbacher wrote:
>>> "P" == Pieter Hintjens writes:
P> Frank, Thanks for your opinion. You hit it spot on, I think. It
P> is really a relief to have security by default without any
P> external packages.
On 03/01/2016 02:51 PM, Roland Fehrenbacher wrote:
>> "P" == Pieter Hintjens writes:
> P> Frank, Thanks for your opinion. You hit it spot on, I think. It
> P> is really a relief to have security by default without any
> P> external packages.
>
> P> Roland, would this work? Pa
On Mar 1, 2016 13:51, "Roland Fehrenbacher" wrote:
>
> > "P" == Pieter Hintjens writes:
>
> P> Frank, Thanks for your opinion. You hit it spot on, I think. It
> P> is really a relief to have security by default without any
> P> external packages.
>
> P> Roland, would this work
Sorry, I was slightly forgetting the details too; Frank's email cleared it up.
There is no point in using an external tweetnacl. If you want an
external security package, build with --with-libsodium. This disables
the built-in tweetnacl and gives you the external dependency you want
as package mai
> "P" == Pieter Hintjens writes:
P> Frank, Thanks for your opinion. You hit it spot on, I think. It
P> is really a relief to have security by default without any
P> external packages.
P> Roland, would this work? Package for Debian using libsodium?
I'm a bit confused now. I t
Frank,
Thanks for your opinion. You hit it spot on, I think. It is really a
relief to have security by default without any external packages.
Roland, would this work? Package for Debian using libsodium?
-Pieter
On Tue, Mar 1, 2016 at 12:03 PM, frank wrote:
> Hi,
>
> I added tweetnacl to libzmq
Hi,
I added tweetnacl to libzmq in 2014 and would like to add my opinion too.
tweetnacl as it is integrated now is very nice for people starting with
compiling from source
e.g. developers using higher level languages like python and requiring
latest code changes.
- it will just work and produce n
> "P" == Pieter Hintjens writes:
P> I can create the repo and the packaging for it, if you like.
That's fine, as long as you don't create a debian subdir in the master
branch. This would get in the way of the official Debian packaging. I'd
manage that in a debian/master branch.
P> W
14 matches
Mail list logo
