This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Originally posted by Stan James: The doc says "Corresponding to each Timer object is a single background thread..." so it sounds like you get a new thread each time you do new Timer(). That would be interesting to confirm.
Yes, each instance of the Timer class should have its own thread. So if you have a task that is long running, (or is schedulling critical), you could consider giving it to its own timer.
Henry [ July 01, 2006: Message edited by: Henry Wong ]