Martin Desruisseaux wrote: > Cory Horner a écrit : >> We are focusing on both concurrency *and* avoiding duplication of >> work in the construction of the Referencing objects. The get() >> method should block precisely because a write lock has been obtained >> and someone is in the process of generating its value. > Yes, I really understand that, but you don't need a read lock at > ObjectCacheEntry for that! We do because the object doing the dispatch - is only operating as a Reader (they never write to the cache). We want them to block on the get method - so they do not start up a bazillion workers to answer the request.
Cheers, Jody ------------------------------------------------------------------------- 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
