quiche
neqo
Our great sponsors
quiche | neqo | |
---|---|---|
23 | 12 | |
8,051 | 1,654 | |
2.1% | 0.9% | |
0.0 | 3.2 | |
10 days ago | 8 days ago | |
Rust | Rust | |
BSD 2-clause "Simplified" License | Apache License 2.0 |
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.
quiche
-
Curl HTTP/3 with quiche discouraged
The issue is dead silent too!
- Best performing quic implementation?
-
Oxy is Cloudflare's Rust-based next generation proxy framework
Even though Oxy is a proprietary project, we try to give back some love to the open-source community without which the project wouldn’t be possible by open-sourcing some of the building blocks such as https://github.com/cloudflare/boring and https://github.com/cloudflare/quiche.
-
How Rust and Wasm power Cloudflare's 1.1.1.1
They’ve been on the Rust train since at least 2019. Just look at projects like quiche, wrangler, and boringtun
-
What is a CDN? How do CDNs work?
It's more like Cloudflare forked nginx a long time ago, and is meanwhile in the very slow (like, decade-long) process of replacing it entirely.
The Cloudflare Workers Runtime, for instance, is built directly around V8; it does not use nginx or any other existing web server stack. Many new features of Cloudflare are in turn built on Workers, and much of the old stack build on nginx is gradually being migrated to Workers. https://workers.dev https://github.com/cloudflare/workerd
In another part of the stack, there is Pingora, another built-from-scratch web server focused on high-performance proxying and caching: https://blog.cloudflare.com/how-we-built-pingora-the-proxy-t...
Even when using nginx, Cloudflare has rewritten or added big chunks of code, such as implementing HTTP/3: https://github.com/cloudflare/quiche And of course there is a ton of business logic written in Lua on top of that nginx base.
Though arguably, Cloudflare's biggest piece of magic is the layer 3 network. It's so magical that people don't even think about it, it just works. Seamlessly balancing traffic across hundreds of locations without even varying IP addresses is, well, not easy.
I could go on... automatic SSL provisioning? DDoS protection? etc. These aren't nginx features.
So while Cloudflare may have gotten started being more-or-less nginx-as-a-service I don't think you can really call it that anymore.
(I'm the tech lead for Cloudflare Workers.)
- Using WebTransport
-
Is it better to learn web development with Python or C?
Ask Cloudflare why they use HTTP/3 and QUIC https://github.com/cloudflare/quiche.
-
Any rust implementations of WebTransport ?
Neqo (Mozilla) and Quiche (Cloudflare) both implement QUIC and HTTP/3. I believe they are both developing an implementation of WebTransport.
- S2n-QUIC (Rust implementation of QUIC)
-
Announcing s2n-quic 1.0
quiche
neqo
- What's the status of Servo right now?
-
Any rust implementations of WebTransport ?
Neqo (Mozilla) and Quiche (Cloudflare) both implement QUIC and HTTP/3. I believe they are both developing an implementation of WebTransport.
- S2n-QUIC (Rust implementation of QUIC)
-
Announcing s2n-quic 1.0
neqo
There is also https://github.com/cloudflare/quiche by Cloudflare and https://github.com/mozilla/neqo by Mozilla.
-
Firefox – Fix parsing of content-length http3 header
Mozilla has a Rust QUIC implementation (one of three good ones in Rust) https://github.com/mozilla/neqo
I'm not sure why it's not used here.
-
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.
-
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
-
QUIC and HTTP/3 Support Now in Firefox Nightly and Beta
Btw, the QUIC library that Firefox relies on is written in Rust: https://github.com/mozilla/neqo
A bit weird though that they didn't cooperate with existing Rust quic stacks like quinn.
The reason is the need to have total flexibility (control). [0]
I reckon to make it as painless as possible to integrate it into Firefox. Also probably a tiny bit of not-invented-here syndrome too :)
What are some alternatives?
quinn - Async-friendly QUIC implementation in Rust
msquic - Cross-platform, C implementation of the IETF QUIC protocol, exposed to C, C++, C# and Rust.
quic-go - A QUIC implementation in pure go
shadowsocks-rust - A Rust port of shadowsocks
udp2raw - A Tunnel which Turns UDP Traffic into Encrypted UDP/FakeTCP/ICMP Traffic by using Raw Socket,helps you Bypass UDP FireWalls(or Unstable UDP Environment)
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
s2n-quic - An implementation of the IETF QUIC protocol
quic - quiwi 🥝 - QUIC implementation in Go.
Rust - All Algorithms implemented in Rust
openmptcprouter - OpenMPTCProuter is an open source solution to aggregate multiple internet connections using Multipath TCP (MPTCP) on OpenWrt
Proxygen - A collection of C++ HTTP libraries including an easy to use HTTP server.
hyperfine - A command-line benchmarking tool