On 8/16/2012 2:01 AM, Andy Seaborne wrote:
Could you give some background as to what you are trying to achieve?
Our current code base works well with GraphMem which throws RuntimeException during reads as a result of concurrent modification, but not during writes.
We basically work with MRSW, and in addition some happy-go-lucky readers, that expect to occasionally have to deal with a RuntimeException from a concurrent modification. The use case for these readers is iterators that are perhaps too tightly tied to a UI, and so the call to next() is waiting for a user click, that may never occur, and at best will be seconds away, rather than milliseconds.
I have morphed the code I attached last time into something that passes our concurrency tests ...., I can send it if you are interested.
Jeremy
