All Implemented Interfaces:
Map
All Known Implementing Classes:
ConcurrentNavigableMap, ConcurrentSkipListMap, ConcurrentHashMap, SubMap
Memory consistency effects: As with other concurrent collections, actions in a thread prior to placing an object into a {@code ConcurrentMap} as a key or value happen-before actions subsequent to the access or removal of that object from the {@code ConcurrentMap} in another thread.
This interface is a member of the Java Collections Framework.
< - K> the type of keys maintained by this map< - V> the type of mapped values1.5 - Doug - Lea| Method from java.util.concurrent.ConcurrentMap Summary: |
|---|
| putIfAbsent, remove, replace, replace |
| Method from java.util.concurrent.ConcurrentMap Detail: |
|---|
if (!map.containsKey(key)) return map.put(key, value); else return map.get(key);except that the action is performed atomically. |
if (map.containsKey(key) && map.get(key).equals(value)) {
map.remove(key);
return true;
} else return false;
except that the action is performed atomically. |
if (map.containsKey(key)) {
return map.put(key, value);
} else return null;
except that the action is performed atomically. |
if (map.containsKey(key) && map.get(key).equals(oldValue)) {
map.put(key, newValue);
return true;
} else return false;
except that the action is performed atomically. |