dysinger / nanomsg-examples Goto Github PK

I have taking the examples and wrapped them up into individual files and scripts, as documented for other's convenience. Use them if you'd like.

src.zip

If arguments are not provided, the examples will segfault (on mac, at least).

I'm trying to compile pubsub.c in my Fedora box, but gcc complains with this:
pubsub.c:2:18: fatal error: libc.h: No such file or directory.

I solved this problem by replacing the libc.h include statement with below:
#include <semaphore.h>
#include <pthread.h>
#include <netdb.h>
#include <time.h>
#include <string.h>
and linked with -lpthread -lanl

PS: Someone post this in stackoverflow: http://stackoverflow.com/questions/21768542/libc-h-no-such-file-or-directory-when-compiling-nanomsg-pipeline-sample

Hi.

See here:
https://github.com/Laeeth/d-nanomsg

I hope it was okay to port your examples to D. I have included them in the repository for ease of use. Please let me know if you are not happy with this - and if you are, could you let me know the license that should apply so I can update the LICENSE file.

Also, I think on your website the reqrep is a duplicate of pipeline (it is correct in your repository).

Thanks.

Laeeth.

who have req/rep with nn_device code example?
thanks a lot

The code for Request/Reply in the blog (http://tim.dysinger.net/posts/2013-09-16-getting-started-with-nanomsg.html) is not the good one. It's the same code as the pipeline. On github it's the good one.

I think it's crucial to understand when to bind (one waiting on sth.) or when to connect (many awaiting sth.).

You actually made a pipeline example where the (one) PULL worker is bound and the (or multiple) PUSH workers are connect'ing to their sockets.
On the other side, the test program in nanomsg shows an example where the (one) PUSH worker is bound and the (or multiple) PULL workers are connect'ing to their sockets.

In a NNanomsg multi REQ/REP example (not just a MsgPack test) using nn_device (RAW REP, RAW REQ), I'm connecting REQ and also connect'ing the REP socket (to their respective bound RAW sockets).

Discovering this by learning in doing, I believe this is crucial to understand nanomsg!

typo?