This is the overflowing (or passivation) policy. we have that in roadmap (and currently have someone looking at it now) but not yet implemented.
You're talking about 3 different issues, which are all on the roadmap:
1: Activation&passivation: we are working on this
2: Write-behind caching. This is also on the roadmap. This will be in the form of a CacheLoader which fronts other CacheLoaders, and buffers all writes, then writes then asynchronously
3: Delegating (clustered) CacheLoader: if an element is not in the cache, we'll try to find it within the cluster.
thanks for your response.
I saw that these features are included in version 1.3. Can you tell what is the tentative release date of this version.
1.3 is a catch-all release, we will most certainly push features out into 1.3.1 or 1.4.
But I'd say the 3 features I mentioned above should make it into 1.3.
1.2.4 should be released by end of August.
With 1.3, we will schedule a dev release 1, maybe 2 But I want to release 1.3 before the end of the year.