Package com.tangosol.net.cache


package com.tangosol.net.cache
Contains classes providing various caching strategies.
  • Class
    Description
    An abstract BinaryEntry-based bundler that serves as a base for BinaryEntryStore operation bundling.
    An abstract base for processors that implement bundling strategy.
    Statistics class contains the latest bundler statistics.
    An abstract base class for the JCache CacheLoader.
    An abstract base class for the JCache CacheLoader.
    An abstract entry-based bundler serves as a base for NamedCache.put() and CacheStore.store() operation bundling.
    An abstract base class for custom cache eviction policies.
    An abstract key-based bundler serves as a base for NamedCache get() and remove() operation bundling as well as the CacheStore load() and erase() operation bundling.
    An abstract base class for serialization-based caches.
    An implementation of the BinaryEntry interface that is based on specified binary key, binary value and BackingMapManagerContext.
    BinaryEntryStore is analogous to the CacheStore, but operates on BinaryEntry objects.
    A UnitCalculator implementation that weighs a cache entry based upon the amount of physical memory (in bytes) required to store the entry.
    A CacheStore that sits directly on top of a BinaryStore.
    Bundling NamedCache implementation.
    An extension of the MapEvent which allows to differentiate between client driven (natural) events and cache internal (synthetic) events.
    TransformationState describes how a CacheEvent has been or should be transformed.
    A JCache CacheLoader.
    A read-only CacheStore that wraps a CacheLoader.
    An extension to the CacheLoaderCacheStore that implements the IterableCacheLoader interface.
    A CacheMap is a Map that supports caching.
    An interface for exposing Cache statistics.
    A JCache cache store.
    A backing Map implementation that delegates all operations to a CacheStore.
    A Map implementation that delegates straight through to a CacheStore.
    Map implementation that wraps two maps - a front map (assumed to be "inexpensive" and probably "incomplete") and a back map (assumed to be "complete" and "correct", but more "expensive") - using a read-through/write-through approach.
    An extension to the CacheMap interface that supports runtime configuration and monitoring of various caching properties.
    A cache Entry carries information additional to the base Map Entry in order to support eviction and expiry.
    EvictionApprover is used to approve the eviction of an entry from the underlying ConfigurableCacheMap.
    An eviction policy is an object that the cache provides with access information, and when requested, the eviction policy selects and evicts entries from the cache.
    A unit calculator is an object that can calculate the cost of caching an object.
    ContinuousQueryCache<K,V_BACK,V_FRONT>
    Create a materialized view of a NamedCache using the Coherence Continuous Query capability.
    A JCache CacheLoader that can iterate its underlying contents.
    A KeyAssociation represents a key object that has a natural association with another key object.
    A LocalCache implementation that supports the JCache API, CacheLoader and CacheStore objects.
    The InternalEvictionPolicy represents a pluggable eviction policy for the non-pluggable built-in (internal) eviction policies supported by this cache implementation.
    The InternalUnitCalculator represents a pluggable UnitCalculator for the non-pluggable built-in (internal) UnitCalculator implementation provided by this cache implementation.
    A CacheStore that sits directly on top of a Map.
    A "near cache" is a CachingMap whose front map is a size-limited and/or auto-expiring local cache, and whose back map is a distributed cache.
    NonBlockingEntryStore provides a means to integrate Coherence with an underlying data source that offers a non-blocking API.
    An Observable Map implementation that wraps two maps - a front map (assumed to be fast but limited in its maximum size) and a back map (assumed to be slower but much less limited in its maximum size).
    The ExpirableStatus adds expiry to the base Status object.
    A CacheEvent that carries a recent value (to avoid it being lost during eviction).
    The Status object is used to manage concurrency at the key level for the key-level operations against the Map, to track all the items in the front Map, to manage the state transition for operations occurring against the Map, and to coordinate events across multiple threads.
    A simple extension of the WrapperNamedCache implementation that shields all content mutating operations such as put(), remove(), lock() etc.
    Backing Map implementation that provides a size-limited cache of a persistent store and supports configurable write-behind and refresh- ahead caching.
    A CacheStore wrapped around a CacheLoader.
    A Map implementation used for a backup map that evicts all data that has been successfully written.
    A synchronization construct used to coordinate asynchronous loads by the refresh-ahead thread with cache accesses by other threads.
    A map listener that follows the "seppuku" pattern, invalidating the Map entries when MapEvents for another related ObservableMap are delivered.
    A version of SerializationMap that implements an LRU policy.
    The InternalEvictionPolicy represents a pluggable eviction policy for the non-pluggable built-in (internal) eviction policies supported by this cache implementation.
    Map implementation that stores its contents in a BinaryStore.
    A version of SerializationMap that implements an LRU policy using time-based paging of the cache.
    A lite BinaryStore implementation used when the real underlying BinaryStore gets destroyed.
    Implementation of the CacheStatistics interface intended for use by a cache to maintain its statistics.
    A UnitCalculator implementation that weighs a cache entry based upon the amount of physical memory (in bytes) required to store the entry.
    A non-observable Map implementation that wraps two maps - a front map (assumed to be fast but limited in its maximum size) and a back map (assumed to be slower but much less limited in its maximum size).
    A combination Filter and Converter used to iterate through the status map in order to iterate through the front keys.
    A stateless Comparator that compares Object.hashCode() values.
    The Status object is used to manage concurrency at the key level for the key-level operations against the Map, to track all the items in the front Map, to manage the state transition for operations occurring against the Map, and to coordinate events across multiple threads.
    Map implementation that stores and accesses its contents through an underlying BinaryStore.
    StoreObserver implementations provide a means for receivers, such as NonBlockingEntryStore, to notify the provider of successful completion (StoreObserver.onNext(com.tangosol.util.BinaryEntry<K, V>)) or unsuccessful completion (StoreObserver.onError(com.tangosol.util.BinaryEntry<K, V>, java.lang.Exception)).
    Defines a NamedMap.Option for asserting the type of keys and values used with a NamedCache.
     
    Deprecated.
    as of Coherence 3.2 all the functionality of this class has been superceded by the ReadWriteBackingMap implementation
    Deprecated.
    as of Coherence 3.2 all the functionality of this class has been superceded by the NearCache implementation
    A simple implementation of NamedCache interface built as a wrapper around any Map implementation.