You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-commits@db.apache.org by ka...@apache.org on 2007/03/24 09:15:05 UTC

svn commit: r521991 - /db/derby/code/trunk/java/engine/org/apache/derby/impl/services/cache/Clock.java

Author: kahatlen
Date: Sat Mar 24 01:15:03 2007
New Revision: 521991

URL: http://svn.apache.org/viewvc?view=rev&rev=521991
Log:
Updated javadoc in Clock to reflect the changes made in DERBY-2114.

Modified:
    db/derby/code/trunk/java/engine/org/apache/derby/impl/services/cache/Clock.java

Modified: db/derby/code/trunk/java/engine/org/apache/derby/impl/services/cache/Clock.java
URL: http://svn.apache.org/viewvc/db/derby/code/trunk/java/engine/org/apache/derby/impl/services/cache/Clock.java?view=diff&rev=521991&r1=521990&r2=521991
==============================================================================
--- db/derby/code/trunk/java/engine/org/apache/derby/impl/services/cache/Clock.java (original)
+++ db/derby/code/trunk/java/engine/org/apache/derby/impl/services/cache/Clock.java Sat Mar 24 01:15:03 2007
@@ -48,11 +48,11 @@
 
 
 /**
-	A cache manager that uses a Hashtable and a ArrayList. The ArrayList holds
-	CachedItem objects, each with a holder object. The Hashtable is keyed
+	A cache manager that uses a HashMap and an ArrayList. The ArrayList holds
+	CachedItem objects, each with a holder object. The HashMap is keyed
 	by the identity of the holder object (Cacheable.getIdentity()) and
 	the data portion is a pointer to the CachedItem. CachedItems that have
-	holder objects with no identity do not have entries in the hashtable.
+	holder objects with no identity do not have entries in the hash map.
 	<P>
 	CachedItems can in various state.
 	<UL>
@@ -469,7 +469,7 @@
 		unkeep does not handle the case of remove.
 
 
-		<P>MT - must be MT-safe.  Getting and deleteing item from the hashtable
+		<P>MT - must be MT-safe. Getting and deleting item from the hash map
 		is in the same synchronized block.  If the cacheable object is waiting
 		to be removed, that is synchronized thru the cachedItem itself
 		(RESOLVE: need to move this sync block to cachedItem instead)