Well, A's put on /a/b/c doesn't become a "remote" put, the entire call is proxied to B. I.e., B handles the put. It becomes local to B, and is treated just as any other tx on B. The purpose of this is so that it can get into the TX Log that A is building up for D. The reason why it isn't just added directly is so that ordering can be maintained. Regarding A's local put on /1/2/3 before D requests a state transfer, perhaps we need to wait for this tx to finish? But in the meanwhile, proxy new local txs on A to B, and start recording remote txs that come in to A? This would bring back the need for idempotency of operations though, since we don't know if the state generated would already contain stuff in the tx log or not. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135903#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...