From: "Hezekiah M. Carty" <hez@0ok.org>
To: Dario Teixeira <dario.teixeira@nleyten.com>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] ZeroMQ vs Nanomsg
Date: Fri, 15 Jul 2016 16:52:51 +0000 [thread overview]
Message-ID: <CAMfPyLDJjregRDkMjZPh2EnX_5_HSUMx=f2VGxO5wrKSbTBOoA@mail.gmail.com> (raw)
In-Reply-To: <f90110dec70c31c6a220a63a701c35d9@nleyten.com>
[-- Attachment #1: Type: text/plain, Size: 874 bytes --]
On Fri, Jul 15, 2016 at 11:58 AM Dario Teixeira <dario.teixeira@nleyten.com>
wrote:
> > I started looking at nanomsg shortly before its original
> > author/maintainer quit the project. I stopped seriously considering
> > nanomsg for my projects at that point. I'm happy to hear that
> > maintenance has been picked back up though. And to echo Simon
> > Cruanes's comment, rgrinberg is also very easy to work with!
>
> Did you look at Nanomsg purely out of curiosity, or did it offer
> something that you found lacking in ZeroMQ?
>
>
Mostly curiosity. I was pretty happy with zeromq but wanted to see what
nanomsg had to offer. There were some intriguing socket/pattern/protocols
in nanomsg (BUS and SURVEY for example) but the better documentation in
zeromq won out because of all the clear examples of the benefits and
pitfalls of zeromq's various socket types.
Hez
[-- Attachment #2: Type: text/html, Size: 1224 bytes --]
prev parent reply other threads:[~2016-07-15 16:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 10:59 Dario Teixeira
2016-07-15 11:25 ` Simon Cruanes
2016-07-15 13:36 ` Dario Teixeira
2016-07-15 11:37 ` SP
2016-07-15 13:42 ` Dario Teixeira
2016-07-15 13:47 ` Hezekiah M. Carty
2016-07-15 15:58 ` Dario Teixeira
2016-07-15 16:22 ` Daniel Bünzli
2016-07-15 16:52 ` Hezekiah M. Carty [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMfPyLDJjregRDkMjZPh2EnX_5_HSUMx=f2VGxO5wrKSbTBOoA@mail.gmail.com' \
--to=hez@0ok.org \
--cc=caml-list@inria.fr \
--cc=dario.teixeira@nleyten.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).