Number of independent accept loops (and listening sockets) per binding. 1 (default): single acceptor, historical behaviour. 0: auto. On platforms with kernel SO_REUSEPORT (Linux 3.9+, macOS/BSD), use min(Environment.ProcessorCount, 16) acceptors; on platforms without it (e.g. Windows), fall back to a single acceptor. >1: explicit count. Requires SO_REUSEPORT; falls back to 1 on platforms that don't support it. Multiple acceptors let the kernel load-balance incoming connections across independent accept threads, removing the single-listener accept bottleneck on many-core machines.

The bindings for the web server to launch with

buffer size for socket operations

A cancellation token for the web server. Signalling this token means that the web server shuts down

Folder for temporary compressed files

The cookie serialiser to use for converting the data you save in cookies from your application into a byte array.

An error handler to use for handling exceptions that are are thrown from the web parts

Optional sink factory for streaming multipart file parts without a temp file. When None (the default), each file part is buffered to a temporary file on disk, matching the pre-existing behaviour.

Enable background connection health monitoring

Interval for connection health checks in milliseconds

Make this true, if you want Suave not to display its server header in every response. Defaults to false.

Home or root directory

Timeout to wait for the socket bind to finish

Maximum age for an active connection before it's considered stuck (seconds)

Maximun upload size in bytes

max number of concurrent socket operations

MIME types

A server-key to use for cryptographic operations. When generated it should be completely random; you can share this key between load-balanced servers if you want to have them cryptographically verify similarly.