tquic - Rust (original) (raw)
Expand description
TQUIC is an implementation of the IETF QUIC protocol. It is a high-performance, lightweight, and cross-platform QUIC library.
§Features and Advantages
- High Performance: TQUIC is designed for high performance and low latency.
- High Throughput: TQUIC supports various congtestion control algorithms (CUBIC, BBR, COPA), and Multipath QUIC for utilizing multiple paths within a single connection.
- High Quality: TQUIC employs extensive testing techniques, including unit testing, fuzz testing, integration testing, benchmarking, interoperability testing, and protocol conformance testing.
- Easy to Use: TQUIC is easy to use, supporting flexible configuration and detailed observability. It offers APIs for Rust/C/C++.
- Powered by Rust: TQUIC is written in a memory-safe language, making it immune to Buffer Overflow vulnerability and other memory-related bugs.
- Rich Features: TQUIC supports all big features conforming with QUIC, HTTP/3 RFCs.
The TQUIC project website offers a comprehensive introduction to TQUIC.
§Get started
See the documents andexamples to get started with TQUIC.
§Feature flags
TQUIC defines several feature flags to reduce the amount of compiled code and dependencies:
ffi: Build and expose the FFI APIqlog: Enable support for qlogh3: Enable support for HTTP/3
pub use crate::connection::path::[Path](connection/path/struct.Path.html "struct tquic::connection::path::Path");
pub use crate::connection::[Connection](connection/struct.Connection.html "struct tquic::connection::Connection");
pub use crate::endpoint::[Endpoint](endpoint/struct.Endpoint.html "struct tquic::endpoint::Endpoint");
pub use crate::error::[Error](error/enum.Error.html "enum tquic::error::Error");
Implementation of QUIC protocol.
A QUIC endpoint.
Error type for quic operations.
Implementation of HTTP/3 and QPACK.
Configurations about QUIC endpoint.
Connection Id is an identifier used to identify a QUIC connection at an endpoint.
Address tuple.
An iterator over FourTuple.
QUIC packet header.
Meta information about a packet.
Statistics about path
Generates purely random connection IDs of a certain length
Available congestion control algorithms.
Available multipath scheduling algorithms.
Important events about path
The stream’s side to shutdown.
The Connection ID MUST NOT exceed 20 bytes in QUIC version 1. See RFC 9000 Section 17.2
The minimum length of Initial packets sent by a client.
The current QUIC wire version.
The QUIC Version 1
The RECOMMENDED value of the timer granularity is 1 millisecond. See RFC 9002 Section 6.1
Generate QUIC connection ID
The PacketSendHandler lists the callbacks used by the endpoint to send packet out.
Used for selecting TLS config according to SNI.
The TransportHandler lists the callbacks used by the endpoint to communicate with the user application code.
Result type for quic operations.