caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Hezekiah M. Carty" <hez@0ok.org>
To: Dario Teixeira <dario.teixeira@nleyten.com>,
	caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] ZeroMQ vs Nanomsg
Date: Fri, 15 Jul 2016 13:47:35 +0000	[thread overview]
Message-ID: <CAMfPyLBALtK3_k3b2GfgLOP9ZQ6s93TUSoJ1BooNbcekPZUF-g@mail.gmail.com> (raw)
In-Reply-To: <9ab1f1de347c6531e51d0757e140a49c@nleyten.com>

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

Hello,

I've been using the zeromq bindings for the last six years or so.  zeromq
has been very nice in my experience - excellent documentation and a helpful
community.  The current and past maintainers of the zeromq bindings have
been very easy to work with.  I wrote the Lwt interface for zeromq -
feedback on that piece is welcome.

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!

Hez

On Fri, Jul 15, 2016 at 6:59 AM Dario Teixeira <dario.teixeira@nleyten.com>
wrote:

> Hi,
>
> 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.)
>
> Thanks in advance for your time!
> Kind regards,
> Dario Teixeira
>
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>

[-- Attachment #2: Type: text/html, Size: 2861 bytes --]

  parent reply	other threads:[~2016-07-15 13:47 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 [this message]
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=CAMfPyLBALtK3_k3b2GfgLOP9ZQ6s93TUSoJ1BooNbcekPZUF-g@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).