For example, assume that the expiration time for entries in the cache is set to 60 seconds and the refresh-ahead factor is set to 0.5. If the cached object is accessed after 60 seconds, a synchronous read from the cache store is performed to refresh its value. On the other hand, if a request is performed for an entry that is more than 30 but less than 60 seconds old, the current value in the cache is returned and an asynchronous reload from the cache store is scheduled. For frequently accessed data, requests won't block waiting for data to be retrieved from persistent store if data expires. Wdyt? Cheers, Mircea _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev

Thanks for the feedback! The way I'm thinking this can be implemented is: add a RefreshAheadInterceptor that, on method return would check weather the entry is in the refresh-ahead timeframe. If so the entry would be place in a queue and another thread would process it. The caller thread would be minimally delayed ( a comparison, no objects created) and we would not have to process all the entries to validate weather they need refresh-ahead, which is more time consuming. Wdyt? Cheers, Mircea On Oct 1, 2009, at 2:06 AM, Sanne Grinovero wrote: > If you integrate this feature I could have on each node a local-only > Infinispan cache A (having values expiring after N minutes and using > "refresh ahead"), which uses as store a distributed Infinispan > cache B > (not expiring); > In this case I could apply updates to the Lucene index stored on > Infinispan B and have the searching nodes use the "local view" > Infinispan A, which would be periodically updated and provide search > latency 0. > > Definitely cool! > > I was planning to implement something like that in user code, but > didn't get the idea of chaining Infinispan caches until your post. > > Cheers, > Sanne > > 2009/9/30 Mircea Markus <mircea.markus(a)jboss.com&gt;: >> For example, assume that the expiration time for entries in the >> cache >> is set to 60 seconds and the refresh-ahead factor is set to 0.5. If >> the cached object is accessed after 60 seconds, a synchronous read >> from the cache store is performed to refresh its value. On the other >> hand, if a request is performed for an entry that is more than 30 >> but >> less than 60 seconds old, the current value in the cache is returned >> and an asynchronous reload from the cache store is scheduled. >> >> For frequently accessed data, requests won't block waiting for data >> to >> be retrieved from persistent store if data expires. >> Wdyt? >> >> Cheers, >> Mircea >> _______________________________________________ >> infinispan-dev mailing list >> infinispan-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/infinispan-dev >> > _______________________________________________ > infinispan-dev mailing list > infinispan-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/infinispan-dev _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev