[infinispan-issues] [JBoss JIRA] (ISPN-5631) NearCache: ability di wait for other Java HotRod clients to invalidate lazy near cache on remove

[ https://issues.jboss.org/browse/ISPN-5631?page=com.atlassian.jira.plugin.... ] Enrico Olivelli commented on ISPN-5631: --------------------------------------- Maybe it could be a flag: Cache<String, String> cache = ...; cache.getAdvancedCache().withFlags(Flag.WAIT_REMOTE_NEAR_CACHES_INVALIDATION) .put("last-login-date", "2012.08.31"); A timeout should be configurable for this kind of operations on the nearcache client side config. Even if it would be expensive for the server I think that this feature will be very useful because with such an ability the hotrod client + nearcache can be used in simple transactions with Last Resource Optimization technique: the client would perform a commit on sql database (or other transactional resource, such as JMS queue) and then invalidate the cache. In fact we use such a tecnique for SQL databases and ActiveMQ queues, and using Infinispan as cache provider sometimes it appens that another (remote) thread which reads data from the nearcache after receiving a JMS message it get a stale value Another useful flag (maybe it would be better to file JIRA issue) is would be a flag to skip the NearCache for "important gets", that is for "get operations" that you want to be in synch with the "real data" stored on the cache servers. -- This message was sent by Atlassian JIRA (v6.3.15#6346)