Re: [zeromq-dev] Cinder-ZeroMQ block

I'm not sure how Cinder works internally but I guess it is similar to OpenFrameworks. It then probably will be typical 'game loop' based. So running anything blocking kills the framerate. You can do a poll with 0 timeout but better would be to replace the sleeping of the loop with polling.

Re: [zeromq-dev] ZeroMQ hackathon/workshop (Brussels, 27/1-29/1 2016)

I'll be a little late the first day - if all goes well I arrive in Brussels at 7:30am that Wednesday morning. Can't wait to see everyone who is going! Brian On Sun, Nov 15, 2015 at 1:57 AM, Trevor Bernard wrote: > I'm very much looking forward to participating at

Re: [zeromq-dev] curveZMQ: authentication / ability to identify peers

First of all: Thanks for your reply! I have read the examples at http://hintjens.com/blog:49 and I like them. What I miss is a way for my application to distinguish between clients. Typically "authentication" implies the ability to know "who" exactly is connecting to you or who you are connecting

Re: [zeromq-dev] curveZMQ: authentication / ability to identify peers

It's not simple and I don't have the examples yet. zmq_msg_gets() lets you know who a message came from. You will want to use the User-Id value, or another value provided by the ZAP handler, taken from the client certificate. On Sun, Nov 15, 2015 at 7:27 PM, Walter B. Rasmann

[zeromq-dev] C4 and CI

Hello list, We've been using parts of C4 to manage the Machinekit project, open-source machine control software. I love the idea of C4, and really buy into its basic ideas of reducing friction of the development process in order to scale the developer and, following that, the user community,

Re: [zeromq-dev] C4 and CI

this question is appropriate for stackoverflow, not the zeromq mailing list. On Sun, Nov 15, 2015 at 10:35 PM, John Morris wrote: > Hello list, > > We've been using parts of C4 to manage the Machinekit project, > open-source machine control software. I love the idea of C4,

Re: [zeromq-dev] curveZMQ: authentication / ability to identify peers

CurveZMQ provides mutual authentication already. The client provides its public key during connection establishment. If the server is authenticating clients (you can choose not to) it checks that public key against public keys it has registered. You have to implement the initial registration

[zeromq-dev] curveZMQ: authentication / ability to identify peers

I'm considering to use curveZMQ for authentication and connection security. Unfortunately I haven't found a way to identify connecting clients. That would be needed in order to see if they are authorized to do stuff on the server, which seems to be a typical use case whenever authentication is