[concurrency-interest] Transactional memory on GCC 4.7.0, what about Java?
aph at redhat.com
Tue Nov 22 11:41:08 EST 2011
On 11/21/2011 10:03 PM, Rémi Forax wrote:
> On 11/21/2011 08:04 PM, Guy Korland wrote:
>> Not all the issues are solved, but it seems like most of the issues
>> have good answers.
>> Also, notice that in .NET they have issues which Java doesn't have
>> like Native code and pointers in C++.
> And how do you solve the IO problems (when you retry) ?
There are basically two practical approaches to I/O:
1. Don't do I/O in a transaction.
2. Convert the transaction into a "relaxed" transaction, i.e. one
that uses a single global lock.
More information about the Concurrency-interest