Floris Bruynooghe
fd8e5bafe0
## Description This moves the FrameStats into the PathStats, allowing us to check what frames where sent on which paths. It then makes the ConnectionStats always be computed to be the sum of all the PathStats. This has as a nice side effect that some stats no longer need to be recorded twice. Which was also error-prone. The PathStats are now boxed in the PathEvent because that variant was now way bigger than any of the other variants. It also fixes a few missed fields in the stats code and uses more defensive code so that won't happen again. ## Breaking Changes Probably none? I'm only adding some fields to PathStats on the public API, while the fields on ConnectionStats remain the same. ## Notes & open questions I need this to be able to write tests that assert frames on specific paths. But I also think that generally this makes more sense. The previous version of the stats was thrown together without much thought I think (by me). I've cleaned up some cargo.toml mistakes that accumulated by using tooling that doesn't follow the sorting/and locations of where things live.
noq
General purpose implementation of the QUIC transport
protocol in pure
Rust. Noq is built as an async-friendly API in the noq crate on top
of a sans-io protocol library in noq-proto.
Noq started out as a fork of the excellent Quinn project. The main focus of development has been towards adding support for more QUIC (draft) extensions:
Features
- Easy to use futures-based async API.
- Client and server server functionality.
- 0-RTT and 0.5-RTT data support.
- Ordered and unordered stream reads.
- Custom and zero-length connection identifiers.
- Fully pluggable crypto API with a Rustls implementation using ring or aws-lc-rs provided by default for convenience.
- Broad platform support, including Linux, Windows, macOS, android, iOS and wasm.
Standards
The noq library aims to be correct implementation of various QUIC standards:
- Supports the core QUIC specifications:
- The standardised QUIC extensions:
- Draft extensions:
- qlog: Structured Logging for Network Protocols.
- QUIC Multipath.
- With experimental qlog support.
- QUIC Address Discovery (QAD).
- Using QUIC to traverse NATs (QNT).
Getting started
Examples at https://github.com/n0-computer/noq/blob/main/noq/examples
$ cargo run --example server ./
$ cargo run --example client https://localhost:4433/Cargo.toml
This launches an HTTP 0.9 server over the QUIC transport on the loopback address serving the current working directory, with the client fetching ./Cargo.toml. By default, the server generates a self-signed certificate and stores it to disk, where the client will automatically find and trust it.
License
Copyright 2025 The quinn developers Copyright 2025 N0, INC.
This project is licensed under either of
- Apache License, Version 2.0, (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)
at your option.
Contribution
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in this project by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.