Pieter Hintjens

Quite separately, if you're working in C I'd strongly recommend using CZMQ, it will make your life much easier. On Tue, Nov 11, 2014 at 3:30 AM, Stefan de Konink...

It is? Surely it's just one additional library.. On Nov 11, 2014 2:07 PM, "Stefan de Konink" [email protected] wrote: > > Quite separately, if you're working in C I'd strongly...

Ah, it usually works better with github, indeed. Sorry for bikeshedding. The code without CZMQ is just harder to understand... actually the test case is opaque and I'm not sure...

As far as I can understand it you're creating and destroying sub sockets. Here is a minimal CZMQ program that does this: ``` #include int main (void) { zsock_t *pub...

Sorry, there was a bug in my example, should have been tcp:// instead of tcp. It asserts in zsock_set_sndhwm() otherwise (pub is NULL), no memory leaks though. So you're saying...

I've no idea how this works internally in libzmq. All I'm concerned with here is reproducing the test to a point where others know what is going on. You may...

Sounds like the same thing, yes. On Wed, Nov 12, 2014 at 12:56 AM, Stefan de Konink wrote: > > I guess it is quite related to the topic "PUSH...

Oh, great! If you really want to give FileMQ an overhaul, take a look at zproto for generating the client and server. :) -Pieter On Thu, Nov 13, 2014 at...

In fact, if you learn zproto you can rebuild FileMQ or similar stacks fairly rapidly. FileMQ has the flaw that you can't upload a file over the protocol, only receive...

The original filemq can be scrapped, really. It was the basis for zproto. If your code is clean and matches our style guidelines, then why not just push it to...