[zeromq-dev] noncontiguous buffers in message frames
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 ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] Just want to say hi
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 wrote: > 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 then we can > integrate it in zproject. > > //Kevin > > 2016-10-14 13:48 GMT+02:00 Wes Young : > >> 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 a local .so properly). >> >> there’s still a ways to go; but idea being you could get czmq / zyre >> bindings from a pip command (testing that is about where i’m at..) >> >> also; adds “pyczmq|pyzyre” into the mix as a module so we can build more >> “pythonic” abstractions on top czmq|zyre while still providing the low >> level stuff “as is” (you can still 'import czmq; ..’) >> >> i’m also assuming by “package management” you’re meaning RPM|PPA, etc.. >> but wanted to throw in pip as well. >> >> fwiw.. >> >> > On Oct 14, 2016, at 2:10 AM, Kevin Sapper >> wrote: >> > >> > - 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 the binding generator and czmq [2] as a example >> for the generated bindings. >> > >> > - A consensus implementation might be useful for zyre [3]. Probably as >> another library on top of zyre. >> > >> >> -- >> wes >> wesyoung.me >> >> >> ___ >> zeromq-dev mailing list >> zeromq-dev@lists.zeromq.org >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev >> > > > ___ > zeromq-dev mailing list > zeromq-dev@lists.zeromq.org > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] Just want to say hi
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 then we can integrate it in zproject. //Kevin 2016-10-14 13:48 GMT+02:00 Wes Young : > 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 a local .so properly). > > there’s still a ways to go; but idea being you could get czmq / zyre > bindings from a pip command (testing that is about where i’m at..) > > also; adds “pyczmq|pyzyre” into the mix as a module so we can build more > “pythonic” abstractions on top czmq|zyre while still providing the low > level stuff “as is” (you can still 'import czmq; ..’) > > i’m also assuming by “package management” you’re meaning RPM|PPA, etc.. > but wanted to throw in pip as well. > > fwiw.. > > > On Oct 14, 2016, at 2:10 AM, Kevin Sapper > wrote: > > > > - 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 the binding generator and czmq [2] as a example for > the generated bindings. > > > > - A consensus implementation might be useful for zyre [3]. Probably as > another library on top of zyre. > > > > -- > wes > wesyoung.me > > > ___ > zeromq-dev mailing list > zeromq-dev@lists.zeromq.org > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] Just want to say hi
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 a local .so properly). there’s still a ways to go; but idea being you could get czmq / zyre bindings from a pip command (testing that is about where i’m at..) also; adds “pyczmq|pyzyre” into the mix as a module so we can build more “pythonic” abstractions on top czmq|zyre while still providing the low level stuff “as is” (you can still 'import czmq; ..’) i’m also assuming by “package management” you’re meaning RPM|PPA, etc.. but wanted to throw in pip as well. fwiw.. > On Oct 14, 2016, at 2:10 AM, Kevin Sapper wrote: > > - 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 the binding generator and czmq [2] as a example for the > generated bindings. > > - A consensus implementation might be useful for zyre [3]. Probably as > another library on top of zyre. > -- wes wesyoung.me signature.asc Description: Message signed with OpenPGP using GPGMail ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Re: [zeromq-dev] ZeroMQ Curve Publish Subscribe
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 directory on my publisher with the public key of the subscriber, and only the subscriber has the private key (and keeps it private). So now only the subscriber can connect to the socket of the publisher. And then they are securely exchanging the data which will be send between publisher and subscriber. Thanks! Greetings, Roy -Original Message- From: zeromq-dev [mailto:zeromq-dev-boun...@lists.zeromq.org] On Behalf Of alex. Sent: Thursday, 13 October, 2016 17:00 To: zeromq-dev@lists.zeromq.org Subject: Re: [zeromq-dev] ZeroMQ Curve Publish Subscribe 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 not mean, however, that this is what actually happens. In fact, ZMQ opens as many (bidirectional) TCP connections between the publisher and all the subscribers and sends pretty much the same message from the publisher to all the subscribers, each in its own connection. What this means for encryption is that the high-level message you send is actually encrypted with the public key of each subscriber and then sent individually. In fact, a single subscriber could never decrypt a message that was sent to another subscriber. TL;DR it just _seems_ as though the publisher is "encrypting" the message once with his private key, but in fact the message is encrypted as many times as there are subscribers. Cheers! alex. Disclaimer: If you are not the intended recipient of this email, please notify the sender and delete it. Any unauthorized copying, disclosure or distribution of this email or its attachment(s) is forbidden. Thales Nederland BV will not accept liability for any damage caused by this email or its attachment(s). Thales Nederland BV is seated in Hengelo and is registered at the Chamber of Commerce under number 06061578. ___ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
