[infinispan-commits] Infinispan SVN: r2167 - in trunk/cachestore/remote: src/main/java/org/infinispan/loaders/remote and 1 other directory.
infinispan-commits at lists.jboss.org
infinispan-commits at lists.jboss.org
Thu Aug 5 05:56:19 EDT 2010
Author: galder.zamarreno at jboss.com
Date: 2010-08-05 05:56:19 -0400 (Thu, 05 Aug 2010)
New Revision: 2167
Modified:
trunk/cachestore/remote/
trunk/cachestore/remote/src/main/java/org/infinispan/loaders/remote/RemoteCacheStore.java
Log:
[ISPN-572] (Update RemoteCacheStore javadoc) Done.
Property changes on: trunk/cachestore/remote
___________________________________________________________________
Name: svn:ignore
- .settings
target
.classpath
.project
+ .settings
target
.classpath
.project
*.iml
*.log
Modified: trunk/cachestore/remote/src/main/java/org/infinispan/loaders/remote/RemoteCacheStore.java
===================================================================
--- trunk/cachestore/remote/src/main/java/org/infinispan/loaders/remote/RemoteCacheStore.java 2010-08-05 09:55:29 UTC (rev 2166)
+++ trunk/cachestore/remote/src/main/java/org/infinispan/loaders/remote/RemoteCacheStore.java 2010-08-05 09:56:19 UTC (rev 2167)
@@ -26,12 +26,10 @@
/**
* Cache store that delegates the call to a infinispan cluster. Communication between this cache store and the remote
* cluster is achieved through the java HotRod client: this assures fault tolerance and smart dispatching of calls to
- * the nodes that have the highest chance of containing the given key.
+ * the nodes that have the highest chance of containing the given key. This cache store supports both preloading
+ * and <b>fetchPersistentState</b>.
* <p/>
- * Due to certain HotRod constraints, this cache store does not support preload and also cannot be used for provide
- * state. Setting <b>fetchPersistentState</b> is not allowed.
- * <p/>
- * Purging elements is also not possible, as HotRod does not support the fetching of all remote keys (this would be a
+ * Purging elements is not possible, as HotRod does not support the fetching of all remote keys (this would be a
* very costly operation as well). Purging takes place at the remote end (infinispan cluster).
* <p/>
*
More information about the infinispan-commits
mailing list