Re: System.Threading.Timers

Yes, Peter, I had intended to have them run their own threads - which
doesn't seem like the best idea.

Peter

> -----Original Message-----
> From: Discussion relating to the specifics of the C# and
> Managed C++ languages [mailto:[email protected]]
> On Behalf Of Peter Ritchie
> Sent: Monday, June 05, 2006 11:43 AM
> To: [email protected]
> Subject: Re: [DOTNET-CX] System.Threading.Timers
>
> By "indpendently 'wait'" do you mean they're running their
> own threads?
>
> On Mon, 5 Jun 2006 09:56:53 -0400, Peter Osucha
> <[email protected]> wrote:
>
> >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...

===================================
This list is hosted by DevelopMentor®  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com