On Fri, Oct 29, 2010 at 12:48 PM, sebb <seb...@gmail.com> wrote: > > Yes, but the code will still need to use the read lock whenever it > reads the field to ensure changes are propagated correctly. > Both the writer and reader threads need to synch. on the same lock in > order for changes to be published safely. > > Not sure using a read/write lock would gain anything over using > volatile - which has the advantage that one cannot bypass it. >
I'm not so concerned with access to the variable itself really. I'm more concerned with a client trying to borrow/return an object while the pool is in the middle of reconfiguring itself. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
