All content with label backing-map.
Related Labels: cache-store , maplistener , refresh-ahead , write-behind , overflow-map , listeners , cluster , versioned-backing-map , synthetic-events , serialization-map , core-concept , serialization-cache , faq-code-examples , local-storage , hashmap , events , synchronous-events , local-cache

Deliver events for changes as they occur (Coherence 3.4 User Guide) Coherence provides cache events using the JavaBean Event model. It is extremely simple to receive the events that you need, where you need them, regardless of where the changes are actually occurring in the cluster. Developers with any experience with the JavaBean model will have ...

Deliver events for changes as they occur (C++) (Coherence 3.4 User Guide) Coherence provides cache events. It is extremely simple to receive the events that you need, where you need them, regardless of where the changes are actually occurring in the cluster. This section contains the following information: Listener interface and Event object In the event model ...

Local Storage (Coherence 3.4 User Guide) Coherence architecture is modular, allowing almost any piece to be extended or even replaced with a custom implementation. One of the responsibilities of the Coherence system that is completely configurable, extendable and replaceable is local storage. Local storage refers to the data structures that actually store or cache ...

read-write-backing-map-scheme (Coherence 3.4 User Guide) readwritebackingmapscheme}} Used in: {{cachingschemes}}, {{distributedscheme}}. Description The {{readwritebackingmapscheme}} defines a backing map which provides a size limited cache of a persistent store. See the ReadThrough, WriteThrough, WriteBehind and RefreshAhead Caching overview for more details. Implementation The {{readwritebackingmapscheme}} is implemented by the class. Cache ...