On Fri, Sep 15, 2017 at 1:46 PM, Garrett D'Amore <garrett@xxxxxxxxxx> wrote:
I don’t have experience with SWIG, since I work primarily in C or Go. The
one drawback I can see is that SWIG appears to be GPLv3, which is a more
restrictive license than nng or nanomsg. It looks like that does not apply
to it’s output, so maybe this is a non-issue.
Another thing that occurs to me is that SWIG seems to just take the C API
and expose it to other runtimes. This may be the simplest way to expose the
API to other languages, but I think it may miss the opportunity to build
APIs that are more idiomatic for those languages. (That said, maybe you can
use SWIG to create a “bottom” layer, and then build an idiomatic API on top
of the SWIG output?)
Still and all, I’m happy to see folks explore and experiment with this
stuff, to find out what works best for them!
On Fri, Sep 15, 2017 at 6:47 AM Michael <mwpowellhtx@xxxxxxxxx> wrote:
I may be interested in applying swig to nng. No sense working harder on
something if swig can generate it for you. Possibly even to embedded
systems, i.e. with nominal cross compilation. I'm thinking of things like
arch-linux, for example. Anyway, let me know what you think.
On September 15, 2017 2:08:34 AM EDT, Garrett D'Amore <garrett@xxxxxxxxxx>
Just a quick note to catch folks up. Nanomsg is still alive, and indeed
I’m working on the next generation (libnng). This library has gone through
a lot of evolution lately, and while it isn’t quite ready for prime time
yet, it probably is ready for folks to begin testing it out.
I can’t promise I won’t break the API in the future (I probably will
actually), but unless you’re using the event API you probably won’t notice.
The nanomsg compatible legacy API will *not* be affected, so you could start
Also, I’ve been working on a new transport, ZeroTier, which allows a L2
style transport using nanomsg over a “global Ethernet”. This is pretty
cool, and you should check out ZeroTier for more on it. (The work on that
transport is a sponsored effort, btw.)
The ZeroTier nng transport is still in development (nearly done though!)
and so I can’t recommend it for use yet. but that will change soon.
At this point, I’m ready to start engaging with other folks who want to
help in the nng effort. The tasks that remain to be done for nng (with
which I can use help) are:
a) Coding. Several transports (TLS, and websocket, possibly others).
Statistics support, more options. Also, I’m interested in working with
folks who want to make nng more performant on various platforms, or port it
to new platforms (embedded systems!)
b) Example programs and documentation. (Especially documentation!)
c) Test coverage. I’ve written a number of test cases, but there remains
opportunity to create a lot more test cases to improve the coverage.
d) New patterns. I think there are some interesting ideas to explore for
developing new patterns, some of which have been discussed here on the list.
I’m happy to work with folks 1:1 who want to help out; if you’ve been
thinking of contributing effort into an open source project, here’s your
opportunity! Just drop me an email!
Sent from my Android device with K-9 Mail. Please excuse my brevity.