>You do know your code has a typo that will cause deadlocks, don't
>you? See below...
><SNIP>
arrgh. i screwed that one up. correcting the typo allows the code
to run fine. ok..i cant prove it with my example code, but under
heavy loads the deadlock does occur....unfortunately im not yet
ready to distribute the code that did produce the deadlock under
heavy loads as open source. :(
i'd recommend against synchronize based on the behaviour i saw
but i cant prove it with example code right now. Dekker's algorithm
with a Thread.sleep(10) at the end seems to be the cure.
-Ys-
Free, encrypted, secure Web-based email at www.hushmail.com
