Uses of Class
io.github.mahmoudimus.quic.connection.ClientConfig

Packages that use ClientConfig

Package	Description
io.github.mahmoudimus.quic	A dependency-free QUIC transport (RFC 9000, 9001, 9002, 9221, 9369).
io.github.mahmoudimus.quic.connection	The sans-I/O QUIC connection and endpoint, ported from quinn-proto: the Connection state machine (handshake, packet assembly and processing, key updates, closing and draining), the Endpoint that routes datagrams and answers with Version Negotiation, Retry and stateless resets, their configurations (TransportConfig, ServerConfig, ClientConfig, EndpointConfig), and the building blocks they are made of: range sets (RangeSet), reassembly of received data (Assembler), buffering of sent data (SendBuffer), streams and flow control (StreamsState), packet number spaces and ACK generation (PacketSpace), loss detection (Recovery), pacing (Pacer), path MTU discovery (MtuDiscovery) and timers (TimerTable).

Uses of ClientConfig in io.github.mahmoudimus.quic

Methods in io.github.mahmoudimus.quic with parameters of type ClientConfig

Modifier and Type	Method	Description
static QuicClient	QuicClient.create(ClientConfig config)	A client on an ephemeral IPv4 port, with the default endpoint settings.
static QuicClient	QuicClient.create(ClientConfig config, InetSocketAddress bindAddress, EndpointConfig endpointConfig)	A client.

Uses of ClientConfig in io.github.mahmoudimus.quic.connection

Methods in io.github.mahmoudimus.quic.connection that return ClientConfig

Modifier and Type	Method	Description
ClientConfig	ClientConfig.Builder.build()	Builds the configuration.

Methods in io.github.mahmoudimus.quic.connection with parameters of type ClientConfig

Modifier and Type	Method	Description
Connection	Endpoint.connect(long now, ClientConfig clientConfig, InetSocketAddress remote, String serverName)	Starts a client connection.
Connection	Endpoint.connect(long now, ClientConfig clientConfig, InetSocketAddress remote, String serverName, SessionCache cache)	Starts a client connection with a cache of session tickets and tokens: it resumes with a ticket from the cache (and sends 0-RTT data if the ticket and the TLS configuration allow it), presents a token from the cache, and keeps the tickets and tokens it receives.