Package com.loomcache.client
@NullMarked
package com.loomcache.client
-
ClassDescriptionAsync wrapper for LoomClient using CompletableFuture and a bounded executor.Immutable client configuration used by failover clients.Ordered blue/green client failover configuration.Client-side cache of the server's partition-to-group ownership snapshot.Client reconnect behavior after the last member connection is lost.Client-side request deduplicator that prevents duplicate sends and coalesces identical in-flight requests.Record representing a request coalescing key.Statistics for request deduplication.Record representing an in-flight request.Client cluster routing mode.Type-safe, locale-independent serializer for client proxy classes.Configuration for periodic client statistics uploads.Per-node connection pool that manages multiple socket connections.Pool health report recordPool statistics record (totalCreated, totalDestroyed, activeCount, idleCount, waitingCount)Connection pool performance and health metrics.Immutable snapshot of connection pool metrics at a point in time.Event emitted when the client creates a local proxy for a distributed object.Listener for client-side distributed-object proxy lifecycle events.Blue/green failover wrapper that connects to one configured cluster at a time.Snapshot delivered to an
InitialMembershipListenerwhen it is registered.Membership listener that also receives the client's current member snapshot on registration.Event emitted when a client lifecycle state changes.Listener for client lifecycle state changes.Client lifecycle states published toLifecycleListeners.Client-side distributed atomic long proxy.Client-side distributed atomic reference proxy backed by the CP subsystem.Fluent builder for batching multiple data-structure operations into a single server-side execution.Fluent builder for map operations within a batch.Fluent builder for queue operations within a batch.Fluent builder for set operations within a batch.Simplified entry point for the LoomCache client SDK.LoomCache Client SDK with smart/unisocket routing, near cache, and production-grade resilience.Listener interface for receiving entry events from the cache.Client-side Consistency Subsystem factory for creating CP primitives.Distributed cache client exception.Client facade for a named distributed executor service.LoomGSet<E>Client-side grow-only set CRDT proxy.Client-side distributed Snowflake ID generator proxy.Client-side distributed countdown latch proxy backed by the CP subsystem.Client-side distributed linearizable lock proxy.LoomList<E>Client-side distributed list proxy.Client-side last-writer-wins register CRDT proxy.LoomMap<K,V> Client-side distributed map proxy.Statistics snapshot for a LoomMap operation.LoomMultiMap<K,V> Client-side distributed multimap proxy.LoomORSet<E>Client-side observed-remove set CRDT proxy.Client-side session-bound PN-counter proxy.Client-side distributed priority queue proxy.LoomQueue<E>Client-side distributed queue proxy.Client-side reliable-topic proxy with replay by retained sequence.Client-side distributed ringbuffer proxy.LoomSet<E>Client-side distributed set proxy.Client-side SQL query result.LoomTopic<T>Client-side distributed topic proxy (publish-subscribe).Client-side facade for a transaction.Event emitted when the client observes a member join or leave its active view.Listener for client-observed membership changes.Controls how the near cache chooses an entry when it must evict for capacity.Strategy for near-cache invalidation with resilience.Invalidation strategy mode.Callback interface for poll-based invalidation.Controls how the near cache treats writes issued by the local client.Configures keys-only persistence for near-cache restart warmup.Configures periodic near-cache anti-entropy checks for missed invalidations.Record representing a cache node endpoint with health and weight information.Tracks node health based on success/failure rates.Node health status enum.Pipelining<E>Bounded in-flight helper for batching asynchronous client operations from one caller thread.Client-side opt-in initiator for thePROTOCOL_HELLO/PROTOCOL_HELLO_ACKhandshake introduced in BLK-2026-04-22-007 Day 1.Outcome of a successful handshake.Raised when a ringbuffer read requests a sequence older than the retained head.Overload policy for reliable-topic publishes when the retained ringbuffer window is full.Raised when a topic poll requests a sequence that the server has already evicted.