caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Simon Cruanes <simon.cruanes.2007@m4x.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 13:25:51 +0200	[thread overview]
Message-ID: <20160715112035.GA947@fuck_yeah.lan> (raw)
In-Reply-To: <9ab1f1de347c6531e51d0757e140a49c@nleyten.com>

[-- Attachment #1: Type: text/plain, Size: 1566 bytes --]

Hi,

I didn't know development of nanomsg had resumed, but it's good news. I
use rgrinberg's onanomsg binding, which works fine for me (although it's
only for a small program), no memleaks, and the API is nice. I think the
bindings are quite mature and rgrinberg is very nice to interact with
;-).

Le Fri, 15 Jul 2016, Dario Teixeira a écrit :
> I'm evaluating ZeroMQ and Nanomsg for the middleware of a distributed
> application.  Now, I know both projects have had a fair share of drama
> in the past, to the point that it's hard for an outside observer to be
> up-to-date on the *current* strengths and weaknesses of each one.  Still,
> it's my understanding that though ZeroMQ is more established, Nanomsg was
> developed later by one of the original authors of ZeroMQ, and supposedly
> fixes some of the architectural mistakes of ZeroMQ.  To complicate matters,
> Nanomsg's author quit the project a while ago, leaving it in limbo for
> a while.  In the meantime, it seems development has picked up again, and
> Nanomsg recently had its 1.0 release.
> 
> Anyway, I'm sure the picture I painted above is incomplete.  Therefore,
> I would be much obliged to hear your opinions and experiences with either
> project.  I will be using the OCaml bindings, obviously, so the maturity of
> the bindings is also a factor.  (On first glance they seem quite complete
> and both offer support for LWT, which is a must.)

-- 
Simon Cruanes

http://weusepgp.info/
key 49AA62B6, fingerprint 949F EB87 8F06 59C6 D7D3  7D8D 4AC0 1D08 49AA 62B6

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-07-15 11:26 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 [this message]
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

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=20160715112035.GA947@fuck_yeah.lan \
    --to=simon.cruanes.2007@m4x.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).