
Signature
Lew
This post contains two requests for information.
>> see:
>> http://gee.cs.oswego.edu/dl/classes/EDU/oswego/cs/dl/util/concurrent/ConcurrentH
ashMap.html
[quoted text clipped - 5 lines]
>
> If so, why?
Thanks to both of you. That is in fact what I'm looking for...
especially the backport to older JVMs at
http://backport-jsr166.sourceforge.net/index.php
Regards
Phil
Lew - 17 Jan 2008 14:26 GMT
>>> see:
>>> http://gee.cs.oswego.edu/dl/classes/EDU/oswego/cs/dl/util/concurrent/ConcurrentH
ashMap.html
[quoted text clipped - 9 lines]
> especially the backport to older JVMs at
> http://backport-jsr166.sourceforge.net/index.php
Based on the Javadocs and unless Gerhard answers my questions, I'm concluding
that one should use the standard API class and not the custom New York EDU
version.
The documentation of the EDU version indicates that it's a pre-Java 5
implementation and doesn't understand the current memory model. They also
talk about it as a replacement for Hashtable of all things, and the
documentation says nothing about generics.
I don't know why anyone would recommend this EDU version over the Java version.

Signature
Lew
Gerhard Aschauer - 18 Jan 2008 12:46 GMT
>>>> see:
>>>> http://gee.cs.oswego.edu/dl/classes/EDU/oswego/cs/dl/util/concurrent/ConcurrentH
ashMap.html
[quoted text clipped - 21 lines]
> I don't know why anyone would recommend this EDU version over the Java
> version.
Lew,
because the Op said that he must be using V1.3.
Regards,
Gerhard
Lew - 18 Jan 2008 14:10 GMT
>>>>> see:
>>>>> http://gee.cs.oswego.edu/dl/classes/EDU/oswego/cs/dl/util/concurrent/ConcurrentH
ashMap.html
[quoted text clipped - 24 lines]
> Lew,
> because the Op said that he must be using V1.3.
Yes, I got that belatedly. Sorry for the opacity.

Signature
Lew
Lew - 17 Jan 2008 14:29 GMT
> Thanks to both of you. That is in fact what I'm looking for...
> especially the backport to older JVMs at
> http://backport-jsr166.sourceforge.net/index.php
How old must your JVM be? The newest JVM not to support it is JVM 1.4, and
that's already in its End-of-Life process and will be retired outright in just
a few months. Java 5 enters End-of-Life this summer if Sun follows its stated
policies and is on time with Java 7.
Anything older than 1.4 is already dead from Sun.

Signature
Lew
This post contains one request for information.
Philipp - 17 Jan 2008 17:09 GMT
>> Thanks to both of you. That is in fact what I'm looking for...
>> especially the backport to older JVMs at
>> http://backport-jsr166.sourceforge.net/index.php
>
> How old must your JVM be?
I wonder how many times I will have to answer this question in this
forum (note that in the original post, I specified that I am looking vor
v.1.3 compatible code).
I am really very sorry, but I am unable to chose the JVM my client is
working with. He obviously has his own reason why to use an 1.3, I can't
change that. (I tried!)
Thanks again for the links which brought me to a solution.
Phil