[jboss-user] [JBossCache] - Re: Transactions
manik.surtani@jboss.com
do-not-reply at jboss.com
Mon Oct 29 12:17:13 EDT 2007
Hi
The differences are that approach 1 treats C as a store of data. Approach 2 treats C as a peer.
Even with approach 1, data changes in C will be picked up by B if the node didn't already exist in B or if the node was evicted. So if your requirement isn't for changes in C to be seen in B *in real time*, then an eviction policy on B will ensure that changes are seen up to a certain delay.
With approach 2, you shouldn't have too much information if all the state in C is relevant to B.
Re: your question on txs, this will still work since changes to the TcpCacheLoader are written in 2 phases as well, a prepare and commit phase and only when B1 or B2 successfully commits will the TcpCacheLoader be instructed to commit changes.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4099900#4099900
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4099900
More information about the jboss-user
mailing list