1) This is great news!
Soon, nng becomes the best light distributed message library in the
messaging ecosystem. The TLS support and incoming web socket support opens
many doors.
The advantages of nng come from
a) compatibility with nanomsg (providing great communication patterns)
b) modular approach and suitability for embedded systems
c) the clean code under the hood
The c) should not underestimated. The messy code of similar libraries
really stops many developers from contributing. The cost of maintenance,
debugging or extending a mess is enormous.
2) "Its still not “production grade”, but I’m ready for folks to begin
kicking the tires a bit harder. I still would prefer folks who find issues
to work with me on reproducible test cases."
What kind of testing would you like to see? Stress tests, performance
tests, sociability, corner cases?
Thanks!
On Wed, Nov 22, 2017 at 1:37 AM, Garrett D'Amore <garrett@xxxxxxxxxx> wrote:
I’ve tagged nng version 0.1. This release has TLS support using mbedTLS —
so you can start playing with connecting over secured networks. (To enable
TLS support you have to configure with -DNNG_TRANSPORT_TLS=ON — I might
make this automatic later, but honestly not very many people are likely to
already have mbedTLS installed on their systems.)
Its still not “production grade”, but I’m ready for folks to begin kicking
the tires a bit harder.
I still would prefer folks who find issues to work with me on reproducible
test cases, so I’d request folks to hold off working on working on language
bindings unless they are comfortable working in C as well.
- Garrett
