This seems likely to yield miserable performance. > while(t.isAlive());
While I don't agree with the approach of spawning a new thread for each request (app servers typically pool threads, and you get one of those for each request already), this might yield (threading pun ;-)) better performance, and should give the same behavior with less wasted CPU cycles (be sure to test it for equivalency, though): t.join(); Holy parenthesized sentence, Batman! Sorry about that. -Max --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
