Quinn Alternatives
Similar projects and alternatives to quinn
-
-
-
SonarQube
Static code analysis for 29 languages.. Your projects are multi-language. So is SonarQube analysis. Find Bugs, Vulnerabilities, Security Hotspots, and Code Smells so you can release quality code every time. Get started analyzing your projects today for free.
-
-
msquic
Cross-platform, C implementation of the IETF QUIC protocol, exposed to C, C++, C# and Rust.
-
-
Scout APM
Less time debugging, more time building. Scout APM allows you to find and fix performance issues with no hassle. Now with error monitoring and external services monitoring, Scout is a developer's best friend when it comes to application development.
-
-
-
-
wezterm
A GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust
-
libcurl
A command line tool and library for transferring data with URL syntax, supporting DICT, FILE, FTP, FTPS, GOPHER, GOPHERS, HTTP, HTTPS, IMAP, IMAPS, LDAP, LDAPS, MQTT, POP3, POP3S, RTMP, RTMPS, RTSP, SCP, SFTP, SMB, SMBS, SMTP, SMTPS, TELNET and TFTP. libcurl offers a myriad of powerful features
-
-
-
-
-
-
advisory-db
Security advisory database for Rust crates published through crates.io
quinn reviews and mentions
-
Choosing a networking library for my game
enet - Golden standard, tested and reliable - Not native rust - Does not seem to be popular in rust turbulence - Readme says it is not stable, but last meaningful commit was 1 year ago - Lacking documentation and examples - Not very popular laminar - Last meaningful release was 3 years ago (ignoring changes that fix typos etc.) - Despite this, everywhere (book, readme) there are mentions that it is under "active development" - Created for Amethyst, which is dead. I am kinda fearful that the same thing will happen to this lib. Tachyon - New and not tested in the battle - Many features that other libraries have planned, Tachyon actually has implemented - Lacking documentation (except for one big readme file), tests, examples Quinn - Big, under active development (daily commits), very popular because web development. - Modular, ability to just use core implemetation: quinn-proto - Do i really need TLS certificates and cryptography for my playing with friends game server? - Stream based, I would need to implement recv/send messages on top of it (not that hard tbh) - Only reliable stream and "unreliable" messages.
-
Any rust implementations of WebTransport ?
I'm personally following the development H3 (Hyperium) (HTTP/3 implementation), which is built on top of Quinn (QUIC implementation). Sadly the project has slowed down due to personal circumstances of its main developer and WebTransport isn't currently in their roadmap.
- S2n-QUIC (Rust implementation of QUIC)
-
Announcing s2n-quic 1.0
quinn
-
Which QUIC crate should I use
As an code hobbyist I'm working on an opensource project where I would be happy to use QUIC. I did a little research and found Quinn and Quiche but also the Mozilla's implementation for which I couldn't find crate Neqo.
- [ANN] Quinn 0.8 (async-enabled pure-Rust QUIC implementation) releases 0.8, first release with QUIC v1 support
-
Crate to build network packets over UDP
Maybe check out laminar and quinn, which implement custom protocols on top of UDP (quinn implements QUIC), to get an idea on how to do things.
-
QUIC is now RFC 9000
Is it possible to compile quicly cli (referenced in the blog post) with musl instead of glibc. I had to add signal.h and it then compiled successfully but I got illegal instruction segfault when executing cli.
There are a few Rust alternatives for QUIC. Anyone tried them and have comments.
https://github.com/cloudflare/quiche
-
UDP Rust Game Server?
See also quinn
-
Experiments with h3 clients + Envoy
quinn-rs/quinn
-
What's everyone working on this week (15/2021)?
I'm using sled for the underlying ACID-compliant, transactional storage engine, and the primary networking protocol is using quinn.
-
mio vs async/await APIs in network protocol library
I searched for other crates doing this and had a little bit of an eye opener looking at quiche and quinn-proto. I came across them before but thanks to your explanation I think I understand their design and separation of crates better now. Summarizing: I would need some kind of core crate that does no networking at all but just packing and unpacking of my protocol-defined messages and implementation of the protocol state machine. Its API would consist of only simple, synchronous functions to handle this. On top of this core crate I could build another crate with more user-friendly API using a specific runtime (async runtimes like async-std and Tokio or event-loop based systems like mio). For interoperability I would provide an FFI layer as simple wrapper of the core crate and then let the foreign languages build a user-friendly API using their own async I/O Frameworks and event-loop. Would you agree to this summary?
Stats
quinn-rs/quinn is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
Popular Comparisons
Are you hiring? Post a new remote job listing for free.