Menu
Does a System.Timers.Timer elapse on a separate thread than the thread that created it?
Lets say I have a class with a timer that fires every 5 seconds. When the timer fires, in the elapsed method, some object is modified. Lets say it takes a long time to modify this object, like 10 seconds. Is it possible that I will run into thread collisions in this scenario?
680
C = Do adalah C - D - E - F - G - A - B - C dengan interval 1 – 1 – 1 – 1/2 – 1 – 1 – 1/2.
Do = C artinya nada do pada tangga nada tersebut tinggi/rendahnya adalah setinggi nada C.
Apabila nada dasarnya – C mayor, maka nada C inilah yang menjadi nada do (C=do / C=1; atau do=C / 1=C).
Lagu daerah ciptaan R.C Hardjosubroto ini dinyanyikan dengan nada dasar Do=C. Artinya nada do pada tangga nada, tinggi atau rendahnya setinggi nada C. Tentu teman-teman masih mengingat pelajaran nada tangga mayor, bukan?
It depends. The System.Timers.Timer has two modes of operation.
If SynchronizingObject is set to an ISynchronizeInvoke instance then the Elapsed event will execute on the thread hosting the synchronizing object. Usually these ISynchronizeInvoke instances are none other than plain old Control and Form instances that we are all familiar with. So in that case the Elapsed event is invoked on the UI thread and it behaves similar to the System.Windows.Forms.Timer. Otherwise, it really depends on the specific ISynchronizeInvoke instance that was used.
If SynchronizingObject is null then the Elapsed event is invoked on a ThreadPool thread and it behaves similar to the System.Threading.Timer. In fact, it actually uses a System.Threading.Timer behind the scenes and does the marshaling operation after it receives the timer callback if needed.
154
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
