Thanks for your answer Dennis.
Does the new unlockedGet method behave like the old incoherent read,
transparently faulting entries when non locally present?
Oh ... new unlocked put/remove are very useful for implementing nested
transactions, thanks much for them :)
Sergio Bossa
Sent by iPhone
Il giorno 10/mar/2010, alle ore 20.14, Chris Dennis <cden...@terracottatech.com
> ha scritto:
Hi Sergio,
The incoherent read options for the map were replaced with direct
incoherent reads of the map itself. So you can instead do:
public V unlockedGet(Object key);
You can also do unlockedPutNoReturn and unlockedRemoveNoReturn
(although you'll want to make sure there is an existing TC
transaction running otherwise you will get a
UnlockedSharedObjectException).
Hope this explains things (and is sufficient for you),
Chris
On Mar 10, 2010, at 2:05 PM, Sergio Bossa wrote:
Hi guys,
I was upgrading my code to use Terracotta 3.2.1 and I discovered that
ConcurrentDistributedMap doesn't seem to support non-coherent reads
anymore: in fact, LockStrategy doesn't have
allowNonCoherentReadsForLocalEntries and
allowNonCoherentReadsForNonExistentMapping settings anymore.
Why such a (odd) change?
Do I have to manually patch ConcurrentDistributedMap to have them
enabled again?
Thanks,
Cheers,
Sergio B.
--
Sergio Bossa
http://www.linkedin.com/in/sergiob
_______________________________________________
tc-dev mailing list
tc-dev@lists.terracotta.org
http://lists.terracotta.org/mailman/listinfo/tc-dev
_______________________________________________
tc-dev mailing list
tc-dev@lists.terracotta.org
http://lists.terracotta.org/mailman/listinfo/tc-dev
_______________________________________________
tc-dev mailing list
tc-dev@lists.terracotta.org
http://lists.terracotta.org/mailman/listinfo/tc-dev