System.Threading.Timers
Peter Osucha <[email protected]>
| Newsgroups | gmane.comp.windows.devel.dotnet.cx |
|---|---|
| Message-ID | <[email protected]> |
I have collection of objects (MyObj) - maybe up to 32 of them - that all need to independently 'wait' for an elapsed time before doing something once a method is called on them. So I have been reviewing what looks like the best option - Timer objects from the System.Threading.Timers namespace. What I am wondering is - what kind of impact having so many active timers might have on my machine, application? When the MyObj objects are created, one argument passed to the constructor tells the object whether it will be using an internal timer so I do have the capability to not automatically create a timer with each MyObj - still, I wonder about having so many timers objects around... Peter =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com