Alawn/Chronicle-Map
1
0
Fork 0
mirror of https://github.com/OpenHFT/Chronicle-Map.git synced 2021-09-13 01:26:12 +00:00
Code Releases Activity

updates around -"acquireUsingLocked"

Browse Source
This commit is contained in:
Rob Austin
2014-12-21 09:28:48 +00:00
parent cb850f03a8
commit 6d1a13745f
1 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+5 -3
View File
@@ -580,10 +580,12 @@ look-ups and making your code run slightly faster.
If you are only accessing ChronicleMap from a single thread. If you are not doing replication
and don't care about atomic reads. Then its simpler ( and faster ) to use acquireUsing() otherwise we
recommend you use `acquireUsingLocked(key,value)`
recommend you use `acquireUsingLocked(key,value)` as this gives you atomicity.
Since the acquireUsing() method can end up creating an entry, the acquireUsingLocked(key,value) method must hold
a segment write lock, this is unlike getUsing(key,using) which only holds a segment read lock.
The acquireUsingLocked(key,value) method holds a segment write lock, as it will update or put a
new entry into the map, this is unlike getUsing
(key,using) which only holds a segment read lock. Below is an example of how to use
acquireUsingLocked(..,..).
``` java
BondVOInterface bond = ... // create your instance