The advantage of TimerTask is that it expresses your intention much better (i.e. code readability), and it already has the cancel() feature implemented. Note that it can be written in a shorter form as well as your own example: Timer uploadCheckerTimer = new Timer(true); uploadCheckerTimer.scheduleAtFixedRate( new TimerTask() { public void run() { NewUploadServer.getInstance().checkAndUploadFiles(); } }, … Read more
Both System.Timers.Timer and System.Threading.Timer will work for services. The timers you want to avoid are System.Web.UI.Timer and System.Windows.Forms.Timer, which are respectively for ASP applications and WinForms. Using those will cause the service to load an additional assembly which is not really needed for the type of application you are building. Use System.Timers.Timer like the following … Read more
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 … Read more
From N3376: 20.11.7.1 [time.clock.system]/1: Objects of class system_clock represent wall clock time from the system-wide realtime clock. 20.11.7.2 [time.clock.steady]/1: Objects of class steady_clock represent clocks for which values of time_point never decrease as physical time advances and for which values of time_point advance at a steady rate relative to real time. That is, the clock … Read more
Keep a reference to the timer somewhere, and use: timer.cancel(); timer.purge(); to stop whatever it’s doing. You could put this code inside the task you’re performing with a static int to count the number of times you’ve gone around, e.g. private static int count = 0; public static void run() { count++; if (count >= … Read more
Handler is better than TimerTask. The Java TimerTask and the Android Handler both allow you to schedule delayed and repeated tasks on background threads. However, the literature overwhelmingly recommends using Handler over TimerTask in Android (see here, here, here, here, here, and here). Some of reported problems with TimerTask include: Can’t update the UI thread … Read more
You can use something like Console.ReadLine() to block the main thread, so other background threads (like timer threads) will still work. You may also use an AutoResetEvent to block the execution, then (when you need to) you can call Set() method on that AutoResetEvent object to release the main thread. Also ensure that your reference … Read more
This is not the correct usage of the System.Threading.Timer. When you instantiate the Timer, you should almost always do the following: _timer = new Timer( Callback, null, TIME_INTERVAL_IN_MILLISECONDS, Timeout.Infinite ); This will instruct the timer to tick only once when the interval has elapsed. Then in your Callback function you Change the timer once the … Read more
Is this what you’re looking for? #include <chrono> #include <iostream> int main() { typedef std::chrono::high_resolution_clock Time; typedef std::chrono::milliseconds ms; typedef std::chrono::duration<float> fsec; auto t0 = Time::now(); auto t1 = Time::now(); fsec fs = t1 – t0; ms d = std::chrono::duration_cast<ms>(fs); std::cout << fs.count() << “s\n”; std::cout << d.count() << “ms\n”; } which for me prints … Read more
The best way is to start the timer thread once. Inside your timer thread you’d code the following class MyThread(Thread): def __init__(self, event): Thread.__init__(self) self.stopped = event def run(self): while not self.stopped.wait(0.5): print(“my thread”) # call a function In the code that started the timer, you can then set the stopped event to stop the … Read more