Hi, I was just wondering how to best implement transactional memory in conjunction with terracotta.
Obviously it could be implemented "on top", with for instance some bytecode instrumentation to intercept field read and write operations. But, as I understand it, Terracotta DSO more or less does this already. So I'm imagining something like a plugin on the client side that can queue up changes in a transaction log over time, and then either commit or roolback these changes. Any thoughts on this? Thanks, -dennis --------------------------------------------------------------------------- The information in this email is confidential and may be legally protected. _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
