Package com.tuladb
package com.tuladb
-
ClassDescriptionA connection credential for MSG_AUTH: a bearer token (JWT/OIDC) or an API key that upgrades the connection's principal and role from the anonymous default.The engine's answer to a successful MSG_AUTH.Auto-batching wrapper: many concurrent callers, few round trips.The batch surface this client drives.A 32-byte transfer id the Base62 (ISO 20022) id mode cannot represent: only bytes 0..25 are public there, and the engine zeroes 26..31 when it runs with
use_iso20022_ref_size = true.Hybrid Logical Clock helpers for TulaDB SDK users.MSG_AUTH was refused: by the engine (LedgerClient.LedgerProtocolException.statusCode()35, ERR_PERMISSION, with the engine's reason) or by the client before anything was sent (LedgerClient.LedgerProtocolException.statusCode()null: empty, too long, or a cleartext credential without the opt-in).A reply that is not a successful answer, as distinct from a transport failure.The engine answered a non-success status: a RESP_ERROR frame carrying its status, or the declined item of a single write.A connect, TLS handshake, write or read did not finish in time.The call was refused before anything was sent: no connection (a failure or timeout closed it, or it was never opened).Socket timeouts, in milliseconds.A fixed set of connections, so N callers get N requests in flight.One row of listAccountBalances: the balance one id holds in one currency of a ledger (engine WireAccountBalanceRow, 64 bytes).An account's identity on wire version 3: (ledgerId, currency, id).Engine AccountMetadataEvent (80 bytes).Leader-aware Ledger client.Backoff between retries of one operation, "full jitter":delay(n)is uniform in[0, min(maxDelayMs, initialDelayMs * 2^n)], where n counts the backed-off retries (0 for the first; the one immediate transport / not-leader retry is not counted).How an operation picks its node.