Martin Desruisseaux wrote: > Not really... I don't see the need for a read lock in an Entry, unless > my modified workflow above if flawed. In my understanding, the > ReadWriteLock is designed for objects like HashMap in a whole, note > individual Map.Entry...
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. In the event the write lock is acquired and we get blocked by something external (such as a slow database request), all the workers would be blocked. Cory. ------------------------------------------------------------------------- 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
