toro/services.cabcard.toro.core.model/ReadinessProbeConfig

ReadinessProbeConfig

data class ReadinessProbeConfig @JvmOverloads constructor(val attempts: Int = 3, val timeoutMs: Long, val backoffMs: Long)

Tuning for the readiness probe run after a session opens.

Opening a session only means the transport stream is up; the PED may still be booting and will silently drop commands sent too early. The SDK therefore probes with a timed command and only reports the connection once the device answers, retrying up to attempts times.

The defaults suit a cold-booting PED. Shortening them trades intermittent connection failures for a faster verdict.

Constructors

ReadinessProbeConfig

@JvmOverloads

constructor(attempts: Int = 3, timeoutMs: Long, backoffMs: Long)

Properties

attempts

val attempts: Int = 3

Number of probes before the connection attempt is reported as failed. Must be at least 1.

backoffMs

val backoffMs: Long

Delay between a failed probe and the next attempt. Must not be negative.

timeoutMs

val timeoutMs: Long

How long a single probe waits for the device to answer. Must be positive.

worstCaseTotalMs

val worstCaseTotalMs: Long

Time the probes and the backoff between them take when the device never answers. It excludes the transport open before each attempt, which the SDK does not time out, so an app-side connect timeout needs headroom for attempts transport opens on top of this value.