[zeromq-dev] Using Strawhouse security pattern with ZeroMQ

I am trying to use Strawhouse security pattern in my zero-mq development. I was following this wiki http://hintjens.com/blog:49 and when I try to run below simple program to make sure I have everything installed, I got an error - #include int main (void) { zctx_t *ctx = zctx_new (); void *publ

Re: [zeromq-dev] Implementing zeromq security

The inproc://zeromq.zap.01 url is hardcoded in libzmq . The session internally creates a client connection to that endpoint. -MinRK ​ On Fri, Dec 12, 2014 at 12:56 PM, Riskybiz wrote: > > I’m trying to implement zeromq se

[zeromq-dev] Implementing zeromq security

I'm trying to implement zeromq security for the first time and WITHOUT using CZMQ. Reading through http://hintjens.com/blog:49 & ZAP protocol info http://rfc.zeromq.org/spec:27 & code at zeromq-4.0.4\tests\tests_security_curve.cpp . I have a question and hope someone might be able to enlighten me

Re: [zeromq-dev] zmq_poll performance question

Hey, I did not check for performance improvement, I simply tested that my program continued to work. The thing is, my poller only has 1 zmq socket and 1 file descriptor (that relies on POLLPRI -- its a GPIO pin). So in my case I could'nt really check for perf improvement. Also I am running this on

Re: [zeromq-dev] event based messaging system

You don't need a timer per request. A typical way to do this sort of scheduling is to keep a queue ordered by event time, by inserting each new event into the queue by comparing event times. You set your single timer's expiration for the event closest to now (eg the head of the queue). When that ev

Re: [zeromq-dev] Majordomo handling malformed messages

We do need to make a new RFC, as the code has gone beyond RFC 18. It's worth making the broker more robust, if you are using it. On Fri, Dec 12, 2014 at 10:05 AM, Lucas Russo wrote: > Hello Everyone, > > I'm using the majordomo protocol to do a service-based thread lookup, > sharing the same con

[zeromq-dev] Majordomo handling malformed messages

Hello Everyone, I'm using the majordomo protocol to do a service-based thread lookup, sharing the same context among all threads. I would like to make the reference majordomo implementation ( https://github.com/zeromq/majordomo/) a little bit more robust against malformed messages. Right now, if

Re: [zeromq-dev] using majordomo broker with asynchronous clients

Vishal, Please see the freelance model; a broker design won't scale to 1M messages a second without significant extra work. -Pieter On Fri, Dec 12, 2014 at 7:57 AM, Vishal Ahuja wrote: > Andre, thank you for your help! I changed the client to send 10k requests at > once, and then send two reque