Expand description
QUIC transport tuning, split by role.
Client (--client-quic-*) and Server (--server-quic-*) carry the
per-connection knobs (stream limits, GSO, timeouts) that each backend applies.
Server additionally owns the knobs that only make sense when accepting
connections: the QUIC preferred address and the QUIC-LB connection-ID encoding.
Each is flattened directly onto crate::ClientConfig / crate::ServerConfig,
so the args parse straight into the config the endpoint is built from. Not
every backend honors every knob, see the field docs.
Structs§
- Client
- The
--client-quic-*transport section. - Resolved
- A resolved view of the per-connection knobs (defaults filled in), shared by
ClientandServerso backends apply them the same way regardless of role. - Server
- The
--server-quic-*transport section. - Server
Id - The routable server ID a QUIC-LB load balancer encodes into connection IDs.
Enums§
- Congestion
Control - The congestion control family for a QUIC connection.