From faf7bf939d9d51ed930a1d9ef3e4744aa1d9693f Mon Sep 17 00:00:00 2001 From: Rob Austin Date: Wed, 5 Nov 2014 09:37:02 +0000 Subject: [PATCH] HCOLL-155 updated java doc to include readlock --- src/main/java/net/openhft/chronicle/map/ChronicleMap.java | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/main/java/net/openhft/chronicle/map/ChronicleMap.java b/src/main/java/net/openhft/chronicle/map/ChronicleMap.java index b12fc13f0..611f9e41a 100644 --- a/src/main/java/net/openhft/chronicle/map/ChronicleMap.java +++ b/src/main/java/net/openhft/chronicle/map/ChronicleMap.java @@ -101,8 +101,8 @@ public interface ChronicleMap extends ConcurrentMap, ChronicleHash { V getUsing(K key, V usingValue); /** - * The method is similar {@link V getUsing(K key, V usingValue);} but in addition locks the - * map segment to operations to be performed atomically. ( see the example below ) + * The method is similar {@link V getUsing(K key, V usingValue);} but in addition read locks + * the map segment to operations to be performed atomically. ( see the example below ) * * Returns the ReadContext which holds a map segment lock and provides method to get the value * ( to which the specified key is mapped) atomically ( see example below for an explanation ), @@ -125,7 +125,7 @@ public interface ChronicleMap extends ConcurrentMap, ChronicleHash { * // add your logic here ( the lock will ensure this bond can not be changed by another thread * ) * - * } // the lock is released here

+ * } // the read lock is released here

* * To ensure that you can read the 'issueDate' and 'symbol' can be read atomically, these values * must be read while the segment lock is in place.