<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">FYI, EHCache uses optional recovery as well.<div><br></div><div><a href="http://ehcache.org/documentation/jta.html#Failure_Recovery">http://ehcache.org/documentation/jta.html#Failure_Recovery</a></div><div><br></div><div><a href="http://ehcache.org/documentation/jta.html#Failure_Recovery"></a><br><div><div>On 11 Mar 2011, at 16:43, Mircea Markus wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi,<div><br></div><div>I've updated tx recovery design document[1] after feedback received from Manik: the most relevant changed is that all recovery information is now stored in a local cache (user can configure it). This way the user is in control of the memory consumed by recovery, being able to passivate to disk this information when/if needed. And all this out-of-the box. </div><div><br></div><div>Cheers,</div><div>Mircea </div><div><br></div><div>[1] <a href="http://community.jboss.org/wiki/Transactionrecoverydesign">http://community.jboss.org/wiki/Transactionrecoverydesign</a></div></div>_______________________________________________<br>infinispan-dev mailing list<br><a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/infinispan-dev</blockquote></div><br><div>
<div><div>--</div><div>Manik Surtani</div><div><a href="mailto:manik@jboss.org">manik@jboss.org</a></div><div><a href="http://twitter.com/maniksurtani">twitter.com/maniksurtani</a></div><div><br></div><div>Lead, Infinispan</div><div><a href="http://www.infinispan.org">http://www.infinispan.org</a></div><div><br></div></div><br class="Apple-interchange-newline">
</div>
<br></div></body></html>