Cory Horner a écrit :
> With a single write lock for the whole map, we would be constrained to
> create a single object at a time, thus making our worker strategy less
> than effective.
Again I agree and already understood that, but the "only write lock" discussion
was for ObjectCacheEntry, not locking for the whole HashMap (in which case Read
/ Write lock is appropriate). Quoting my previous email:
"In my understanding, the ReadWriteLock is designed for
objects like HashMap in a whole, not individual Map.Entry"
So there is my proposal: I will commit a ObjectCache2 class (without any
ObjectCacheEntry class) so you can see my point. It will use the modified
workflow that I tried to explain in my previous email.
Martin
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
