On Wed, 21 Jul 2004 05:17:05 +0900, you wrote:

>> pretty heavily, with threaded code and the resource never gets
>> corrupted..

>That's not a proof - at best it's an indication. :-)

well if it gets corrupted, there will  e be a problem with the mutex
synchronization method. the resource is only accessed in a synchronize
block...

>Synchronizing with mutexes is another way to make method thread safe.

that's what i'm doing. it seems to be working well, no matter what i
throw at it...

of course, when i eventually release it and if it gets wider spread
use, that will be the real test.



http://home.cogeco.ca/~tsummerfelt1