Actually, the MD5 thingy is an attempt to generate a unique temp lock ID, IIRC. so this piece of code can disappear entirely now that the tests concurrency is better.
As for the other threads that are left running, I couldn't track down yet the warning from the benchmark tests, but I'd love to get rid of those false warnings. I thought the stack trace could at least tell us who spawned the thread, but obviously it's not always clear. Shai On Saturday, December 25, 2010, Robert Muir <[email protected]> wrote: > On Sat, Dec 25, 2010 at 4:04 AM, Uwe Schindler <[email protected]> wrote: >> Md5 is guaranteed to be there (like utf8 as charset). This is documented in >> crypto Api, which algorithms are available for digest. >> > > where is this documented? its not in the javadocs. > > anyway, we shouldn't be doing this: > * this algorithm might not exist on J2ME etc (still java), you need to > install an extra crypto add-on. > * we shouldnt start up an expensive PKI infrastructure on mac os X, > including spawning a new thread, just to hash a string. thats absurd. > * we pay all these costs ... for md5! its not even a good hash! > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
