commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun Thomas" <>
Subject RE: TimerMap
Date Mon, 24 Nov 2003 20:50:30 GMT
Actually, I'm only concerned about keySet().iterator() and values().iterator().  Not about
keySet() and values() :)  
Perhaps something that can be worked in as we move forward?  I think this (the "ill-formedness"
of the iterators) could be something captured in docs today and implemented explicitly moving
forward.  Perhaps I'll take a shot once we've got it checked in.... 

Now if only I can find my password for CVS :) I should be able to check it in....  


-----Original Message-----
From: James Carman [] 
Sent: Monday, November 24, 2003 12:42 PM
To: 'Jakarta Commons Developers List'
Subject: RE: TimerMap

Maybe you could just go ahead and throw UnsupportedOperationException on keySet(), but implement
a generic debugCachingIssues() method!  ;-)

-----Original Message-----
From: Joseph Rosenblum [] 
Sent: Monday, November 24, 2003 3:40 PM
To: Jakarta Commons Developers List
Subject: Re: TimerMap

Hey there,

Thanks for all the feedback! Ideally, I think this makes the most sense 
as a Map --since it's most common use cases are as a Map-- and the 
javadoc would spell out usage scenarios and challenges (something I 
will work on).

I've changed two points: TimedMapKey is now private and the backing 
store is no longer synchronized (as per Arun's suggestions). 
Synchronization can be left to the client developer.

Even though I wouldn't want to have client code accessing entries via 
iterator in normal usage, I don't think calling keySet() should throw 
an UnsupportedOperationException since examining the keySet of such a 
map could be very useful in debugging caching issues.



Joseph Rosenblum | 25th Street Networks
Easy, Reliable Web Hosting @

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message