aioquic
quiche
aioquic | quiche | |
---|---|---|
6 | 26 | |
1,545 | 8,928 | |
1.9% | 1.3% | |
8.5 | 9.0 | |
about 2 months ago | about 19 hours ago | |
Python | Rust | |
BSD 3-clause "New" or "Revised" License | BSD 2-clause "Simplified" 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.
aioquic
-
WinBtrfs – an open-source btrfs driver for Windows
One of the interesting patterns happening in Rust is io-less libraries. I'm not sure where best to link this phenomenon. It here s a open issue for an io-less quic library, from 2019, https://github.com/aiortc/aioquic/issues/4
It'd be so fracking sweet to see filesystems follow this pattern. If we could re-use the file system logic, but apply it to windows or fuse or Linux or wasm linearly-addressed-storage, that would allow such intensely cool forms of portability/reuse & bending/hacking.
- WebGPU – All of the cores, none of the canvas
-
Granian – a Rust HTTP server for Python applications
for those wishing to use http3 with a Python web framework, the ASGI hypercorn[1] currently supports it.
made a Django example last week with a sample client based on the examples from aioquic[2]: https://github.com/djstein/django-http3-example
this example also includes the first pass at async Django REST Framework using adrift[3] based on these GitHub issues:
- https://github.com/encode/django-rest-framework/pull/8617
- https://github.com/encode/django-rest-framework/issues/8496
sources
[1]: https://github.com/pgjones/hypercorn
[2]: https://github.com/aiortc/aioquic
[2]: https://github.com/em1208/adrf
- Caddyhttp: Enable HTTP/3 by Default
-
Is it better to learn web development with Python or C?
In your estimation where does the QUIC specification, HTTP/3 specification, WebTransport specification, aioquic QUIC and HTTP/3 implementation in Python https://github.com/aiortc/aioquic (notice the GoogleChrome/samples WebTransport sample code is described as local server "There's code for a sample local server at https://github.com/GoogleChrome/samples/blob/gh-pages/webtransport/webtransport_server.py") fit into the categories you color "Framework" and "Webserver"?
-
HTTP/3: Practical Deployment Options (Part 3)
Whilst the article rightly mentions aioquic to use HTTP/3 with Python, it is only a minimal example server. Hypercorn is a compete ASGI server built on aioquic that is likely more useful practically.
quiche
-
Nghttp3 1.0.0 – HTTP/3 library written in C
The title of this post puts emphasis on "written in C", making me wonder when this would ever be a desirable feature, given that more secure implementations are available, and can be integrated into old C projects just as easily.
No need to rewrite everything from the ground up: https://github.com/cloudflare/quiche#curl
-
Curl HTTP/3 with quiche discouraged
The issue is dead silent too!
https://github.com/cloudflare/quiche/issues/1115
- 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.
- DNS-over-HTTP/3 in Android
-
The MQTT broker powering Cloudflare's new Pub/Sub product is written in Rust!
Cloudflare has used rust for multiple projects in the past such as their QUIC/HTTP3 implementation Quiche and a WireGuard implementation BoringTun.
What are some alternatives?
hypercorn - Hypercorn is an ASGI and WSGI Server based on Hyper libraries and inspired by Gunicorn.
quinn - Async-friendly QUIC implementation in Rust
Twisted - Event-driven networking engine written in Python.
msquic - Cross-platform, C implementation of the IETF QUIC protocol, exposed to C, C++, C# and Rust.
django-http3-example - Example Repo of Django using HTTP/3
quic-go - A QUIC implementation in pure Go
hypercorn
shadowsocks-rust - A Rust port of shadowsocks
mitmproxy - An interactive TLS-capable intercepting HTTP proxy for penetration testers and software developers.
neqo - Neqo, an implementation of QUIC in Rust
sslyze - Fast and powerful SSL/TLS scanning library.
s2n-quic - An implementation of the IETF QUIC protocol