I do confirm this behavior.<div><br></div><div>Transactions and asynchronous updates may seem antagonistic, but they are not on a multi-level cache.</div><div>I plan to use a synchronous transactional disk cache and a second non transactional asynchronous s3 cache, to get the best of both worlds.</div>
<div><br></div><div>Since the asynchronous aspect of the s3 cache will not allow me to get any feedback (aka Future), I want it to 'write-behind' in the background (and hope everything goes well).</div><div><br></div>
<div>I will wait for the qi4j v1 release (probably Monday), adapt infinispan to the blobstore of jClouds and take a closer look at this in a couple of weeks. </div><div><br></div><div>Phil<br><br><div class="gmail_quote">
On Sat, Jan 23, 2010 at 12:58 PM, Amin Abbaspour <span dir="ltr"><<a href="mailto:a.abbaspour@gmail.com">a.abbaspour@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi All,<br>
<br>
Regarding <a href="http://community.jboss.org/wiki/Write-ThroughAndWrite-BehindCaching" target="_blank">http://community.jboss.org/wiki/Write-ThroughAndWrite-BehindCaching</a><br>
, Even if Syncer is in Async mode, but if we modify a key inside a<br>
transaction boundary it is always stored synchronously! Why is it so?<br>
How can I have both locking and async store. FYI I use JBossTM<br>
Standalone.<br>
<br>
Regards,<br>
<font color="#888888">Amin Abbaspour<br>
_______________________________________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
</font></blockquote></div><br></div>