Ok, there we go, a well encapsulated form of the desired pattern. Yes, let's use this instead as I think we have no guarentees of correct behavior on multi-processor systems with heirachal memory caches.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Toby Allsopp" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, February 13, 2003 11:46 AM Subject: Re: [JBoss-dev] Why are we using this bogus construct > I'd just like to say that I believe David is exactly right here. I've > been following (or rather trying and failing most of the time) the > javaMemoryModel (http://www.cs.umd.edu/~pugh/java/memoryModel/) mailing > list, and this kind of issue is very difficult to analyse correctly. > > My advice, FWIW, is to stop messing around and just use util.concurrent > by Doug Lea > (http://gee.cs.oswego.edu/dl/classes/EDU/oswego/cs/dl/util/concurrent/intro.html). > There aren't many people who can prove that their tricky concurrent Java > code is correct, but Doug Lea can. Just use > EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap and sleep at > night. > > Toby. ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
