From: Dario Teixeira <dario.teixeira@nleyten.com>
To: SP <sp@orbitalfox.com>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] ZeroMQ vs Nanomsg
Date: Fri, 15 Jul 2016 14:42:02 +0100 [thread overview]
Message-ID: <eddb529e937b28316785d0c0c2c338b6@nleyten.com> (raw)
In-Reply-To: <20160715113708.GF5091@tiger>
Hi,
> What I'm curious about is how interoperable they are. Can one switch
> between the two back-ends or bindings? Does either of them "wrap" the
> other?
Someone please correct me if I'm wrong, but my impression is that
there's no interoperability at all between ZeroMQ and Nanomsg.
Cheers,
Dario
next prev parent reply other threads:[~2016-07-15 13:42 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 [this message]
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=eddb529e937b28316785d0c0c2c338b6@nleyten.com \
--to=dario.teixeira@nleyten.com \
--cc=caml-list@inria.fr \
--cc=sp@orbitalfox.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).