Rüdiger Klaehn b212bbcacc deps: Hide the tokio streams behind simple newtype wrappers (#547)
## Description

Hide the 2 usages of broadcast::Receiver behind a newtype wrapper that
implements Stream.

Hide the 1 usage of watch::Receiver behind a newtype wrapper that
implements Stream.

## Breaking Changes

noq::Connection::path_events: now returns a PathEvents struct
noq::Connection:: nat_traversal_updates: now returns a
NatTraversalUpdates struct
noq::Connection:: observed_external_addr: now returns a
ObservedExternalAddr struct

## Notes & open questions

Note: I did a very simple wrapper for watch::Receiver<SocketAddr> since
SocketAddr is Copy, and the main complexity of watch::Receiver is to
allow to borrow the underlying value. We don't need that. The only fn is
get which allows you to sync get the current value or none if none
present yet.

For the two broadcast receiver wrappers the public API is just Stream.
You get notified if you miss events with a Lagged error, and you can
always grab a new one if you want to start from now.

I did not try to abstract over the 2 different broadcast wrappers.
Better to have distinct types.

---------

Co-authored-by: Floris Bruynooghe <flub@n0.computer>
2026-03-26 14:23:29 +00:00
2026-02-06 10:04:56 +00:00
2026-03-09 14:41:38 +01:00
2025-03-24 15:57:34 +00:00
2026-03-09 14:42:54 +01:00
2026-03-09 14:40:18 +01:00
2020-01-27 10:21:10 -08:00
2026-03-09 14:45:33 +01:00
2025-02-23 11:52:46 +00:00

noq

Documentation Crates.io Chat License: MIT License: Apache 2.0

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:

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

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.

S
Description
noq, a QUIC implementation in Rust
Readme 106 MiB
Languages
Rust 99.3%
Python 0.5%
Shell 0.2%