nng
nng copied to clipboard
nanomsg
Investigate QUIC transport
A QUIC transport has been written for mangos (though not integrated yet) -- we should look at this for nng. It may be even more useful than KCP.
Interesting. Too bad it depends on openssl but maybe I can convert it to use our aio and ssl framework. On Thu, Feb 15, 2018 at 2:18 PM Brad Jones [email protected] wrote:
FYI: https://github.com/h2o/quicly
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/nanomsg/nng/issues/230#issuecomment-366080420, or mute the thread https://github.com/notifications/unsubscribe-auth/ABPDffQhrcAHSlKBzyPes4KLvkdo2XcFks5tVK0WgaJpZM4R55GC .
The QUIC transport that was written for mangos has some issues that should be addressed, so I don't think I'm ready to write one for NNG yet, until the issues with that other one are sorted out. (Specifically there are some opportunities to improve the protocol to eliminate a round trip, and I have concerns about the way it multiplexes streams based on a string.)
I'm interested in a good messaging protocol over QUIC (possibly looking at Facebook's https://github.com/facebookincubator/mvfst). Has there been any change in the issues @gdamore noted above, or any further work on Nanomsg over QUIC?
I haven't had a chance to look at this recently -- but the mvfst project seems to hold some promise. I wish it were in C, but we can probably ignore that and link to it directly. (C++ tends to give the linker fits and greatly slows down the build, in my experience.)
In terms of the mangos port, that's probably something I need to revisit as well. I've been working on mangos stuff recently trying to knock out a bunch of bugs and improve the overall test coverage.
Right now I'm not getting paid for work on NNG, so it has reverted to "as I have time" status, in favor of work that pays the bills.