Hi Alex,
Thanks for your answer and explanation. It is now a bit more clear.
I also gave a look on the blogs of Pieter and this private / public key system
is for authenticating the subscribers and after you are authenticated some
short-term keys are exchanged.
So what I did, I created a .curve
i started banging away sort of at this:
https://github.com/wesyoung/pyzyre
https://github.com/wesyoung/pyczmq
these leverage what pyzmq did in terms of “build the C stuff from source and
embed the .so locally, use the generated c-bindings on top of that” (made some
patches to zproject to load
Hi,
I wrote some code to support noncontiguous buffers in message frames -
https://github.com/maxkozlovsky/zeromq4-1/commit/befc4e1c7de
dbf0b9e5641d19e877a19f0f6db16.
Please let me know if you would like to use it in some form, I can get it
to more production quality if necessary.
Max
I have once published a python package onto pypi. There are also tools like
Wercker that allow to do certain actions upon some triggers happening on
Github. I think it is possible to automate the publish chain after a
successful build. I'll look at it.
On 14 October 2016 at 14:06, Kevin Sapper
Hi Mehdi,
welcome to the community! If you like to contribute, here are some random
thoughts:
- As you seem to know python. For our C projects we have binding generators
for python which work fine but the binding code is currently not deployed
to a package management system.
See zproject [1] for
Hi Wes,
Neat!
By "package management" I've referred to pip or easy_install (not sure if
they're the same) which are the common way to install python libraries.
It would be really great if we could integrate this into our automatic
deployment. Whenever the pip deployment is ready let me know
