NanoSDK
lsquic
NanoSDK | lsquic | |
---|---|---|
2 | 5 | |
112 | 1,453 | |
0.9% | - | |
9.2 | 7.2 | |
8 days ago | about 2 months ago | |
C | C | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
NanoSDK
-
MQTT Communication Optimization Practices for Internet of Vehicles Mobile Scenarios
We recommend using QoS 1 for sending important data on the automotive side and using MQTT SDK with QoS retransmission capability and built-in QoS message window (queue), such as NanoSDK, which features asynchronous acknowledgment, built-in QoS message queue, automatic retransmission, and high throughput and consumption capabilities.
-
MQTT over QUIC: Next-Generation IoT Standard Protocol
NanoSDK 0.6.0 has released the first C language MQTT over QUIC SDK based on the MsQuic project.
lsquic
-
Avoiding HTTP/3 (for a while) as a pragmatic default
I referred to sockets as an API design, not to express an opinion on whether you should place your protocol implementations inside or outside the kernel. (Although that’s undeniably an interesting question that by all rights should have been settled by now, but isn’t.)
Even then, I didn’t mean you should reproduce the Berkeley socket API verbatim (ZeroMQ-style); multiple streams per connection does not sound like a particularly good fit to it (although apparently people have managed to fit SCTP into it[1]?). I only meant that with the current mainstream libraries[2,3,4], establishing a QUIC connection and transmitting bytestreams or datagrams over it seems quite a bit more involved than performing the equivalent TCP actions using sockets.
[1] https://datatracker.ietf.org/doc/html/rfc6458
[2] https://quiche.googlesource.com/quiche
[3] https://github.com/microsoft/msquic
[4] https://github.com/litespeedtech/lsquic
- The Illustrated QUIC Connection
-
LiteSpeed QUIC (LSQUIC) is an open-source implementation of QUIC and HTTP/3
> the word "thread" does not appear anywhere.
because it doesn't use threads? The library is intended to be used inside an eventloop. I think the same also applies for other typical transport libraries - e.g. HTTP/2 or TLS ones.
> Not sure why one would choose this over QUICHE.
I think there are certainly reasons. lsquic seems a lot more optimized than quiche and most other libraries out there. It makes use of some pretty clever datastructures (e.g. https://github.com/litespeedtech/lsquic/blob/master/src/libl...), and likely has a drastically lower rate of heap allocations than other implementations. Some of those things - like the use of intrusive linked lists - are unfortunately not that easy to apply in Rust.
I wouldn't be suprised if lsquic outperforms various other implementations - and if that's important to users it might be a reason to choose it (but as always: measure for your use-case).
I personally also think Rust is the way to go for system level code. But I wouldn't dismiss a project for not using Rust. And this one at least has a fair set of unit-tests, so it looks to me a lot more sane than a lot of other C based projects.
What are some alternatives?
nanomq - An ultra-lightweight and blazing-fast Messaging broker/bus for IoT edge & SDV
msquic - Cross-platform, C implementation of the IETF QUIC protocol, exposed to C, C++, C# and Rust.
nghttp3 - HTTP/3 library written in C
ssldump - ssldump - (de-facto repository gathering patches around the cyberspace)
quic - In-kernel QUIC implementation with Userspace handshake
starlink-coverage - Calculating some statistics about Starlink satellites
CocoaMQTT - MQTT 5.0 client library for iOS and macOS written in Swift
mvfst - An implementation of the QUIC transport protocol.
NanoSDK - NanoSDK - MQTT 5.0-compliant SDK with QUIC support in NNG flavor [Moved to: https://github.com/emqx/NanoSDK]
netty-incubator-codec-quic
quant - QUIC implementation for POSIX and IoT platforms
ENet-CSharp - Reliable UDP networking library