I can imagine extending nng to run over LTP. I suppose you’d probably make
most of the transports “green”, but REQ/REP frames would be “red”.
The thing is that nanomsg and nng already have this separation, at the
layer above. This mapping may lead to some interesting capabilities on top
of a transport that can express these needs separately — but it would take
some effort to experiment and build such a thing. I have no experience or
knowledge of LTP before this. I guess I haven’t needed to communicate over
a deep space network before, but this is kind of cool.
- Garrett
On Tue, Jan 2, 2018 at 10:12 AM Karan, Cem F CIV USARMY RDECOM ARL (US) <
cem.f.karan.civ@xxxxxxxx> wrote:
Hi Garrett, a quick question about the extensibility of nng; is it
possible to extend it to support red and green parts similar to the
Licklider Transmission Protocol (see towards the end of the Design section
for definitions of red and green:
https://en.wikipedia.org/wiki/Licklider_Transmission_Protocol#Design)
<https://en.wikipedia.org/wiki/Licklider_Transmission_Protocol#Design)?> ?
I can see a lot of practical use cases where only portions of a stream need
to be guaranteed delivery, but I can also see how this is not a current
focus of nng. I just want to know if the current framework is flexible
enough to support it.
Thanks,
Cem Karan
------------------------------
*From:* nanomsg-bounce@xxxxxxxxxxxxx [nanomsg-bounce@xxxxxxxxxxxxx] on
behalf of Garrett D'Amore [garrett@xxxxxxxxxx]
*Sent:* Saturday, December 30, 2017 10:17 PM
*To:* nanomsg@xxxxxxxxxxxxx
*Subject:* [Non-DoD Source] [nanomsg] nng version 0.2.0 — Happy New Year!
Happy New Year (a little early)!
In the spirit of celebration of the year 2018, I’m pleased to announce
that nng — that is nanomsg-next-gen — version 0.2.0 is now released.
For those of you who have not been following, nng represents my effort
to completely redesign a modern nanomsg framework that can grow to support
new technologies and capabilities, and succeed in ways that nanomsg itself
was unable.
This is a pre-release, but I consider it “beta" level of stability. It
still has some maturing to do, and some important functionality is missing,
but already it is quite usable. Barring the lack of adequate documentation
and certain performance elements, I believe this version to be superior to
the official nanomsg in most regards.
This release adds secure websocket support, using the wss:// scheme, which
means it is now possible to use TLS v1.2 and websocket together. It also
supports multiple sockets using the same TCP port when using either wss://
or ws:// schemes — the server will discriminate based on the full URL (or
in some cases, the value of Host:)
In the coming weeks and months, expect much more complete documentation,
performance improvements, observability improvements (actual statistics!),
and some interesting new capabilities for web applications and people
wanting to build gateways between the web and nanomsg applications.
For folks that want to participate and help, give me a shout. There are
still lots of ways to assist, and things to do.
— Garrett
