Skip to main content

Timer - run action at a specific time interval

Nu odată am întâlnit requirement-uri la o aplicație de genul:
Se da un proces ce trebuie executat la un anumit interval de timp. Un proces se poate executa doar dacă a trecut un anumit interval de timp de la terminarea ultimei procesări.
Exista mai multe soluții la aceasta problema. Thread-uri, timer, sleep and so on. Pentru a vedea cum se folosește un timer click aici.
Soluția care mi-e mi s-a părut cat de cat curata se bazează pe un timer setat sa ruleze o singura data, iar după fiecare procesare acesta este pornit din nou.
Trebuie avut grija la următoarele posibile probleme care pot sa apară:
     1. Când se face Start, Stop la timer trebuie avut grija ca suntem într-un mediu multi-thread, din aceasta cauza trebuie sa ne asiguram ca avem un mecanism de lock-ing.
     2. La fiecare execuție a callback-ului pe care timer-ul îl arunca trebuie verificat dacă timer-ul nu a fost oprit deja prin intermediul altui thread.
     3. In callback trebuie sa avem grija sa avem grija sa prindem excepțiile care pot sa apară din codul nostru înainte sa dam drumul la timer. Altfel ne putem trezi ca după o eroare timer-ul nu mai funcționează deși noi ne-am aștepta sa ruleze în continuare.
Mai jos găsiți implementarea pe care eu o propun:
public class CustomTimer
    {
        private readonly Timer _timer;
        private readonly object _timerPadLock = new object();
        private bool _timerStarted;

        private readonly int _timeInterval;
        private readonly Action _action;


        public CustomTimer(TimeSpan timeInterval,Action action)
        {
            _timeInterval = Convert.ToInt32(timeInterval.TotalMilliseconds);
            _action = action;

            _timer = new Timer(
                TimerCallback,
                _timer,
                Timeout.Infinite,   // When set to infinite the timer is not started automatically.
                Timeout.Infinite);
        }

        public void Start()
        {
            if (!_timerStarted)
            {
                lock (_timerPadLock)
                {
                    if (!_timerStarted)
                    {
                        _timerStarted = true;
                        RunTimer();
                    }
                }
            }
        }

        public void Stop()
        {
            lock (_timerPadLock)
            {
                _timerStarted = false;
            }

        }

        private void TimerCallback(object state)
        {
            if (!_timerStarted)
            {
                return;
            }

            try
            {
                // Invoke custom action.
                _action.Invoke();
            }
            catch (Exception ex)
            {
                // Exception handling
            }


            RunTimer();
        }

        private void RunTimer()
        {
            _timer.Change(_timeInterval, Timeout.Infinite);
        }
    }

Comments

Popular posts from this blog

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

Fundamental Books of a Software Engineer (version 2018)

More then six years ago I wrote a blog post about fundamental books that any software engineer (developer) should read. Now it is an excellent time to update this list with new entries.

There are 5 different categories of books, that represent the recommended path. For example, you start with Coding books, after that, you read books about Programming, Design and so on.
There are some books about C++ that I recommend not because you shall know C++, only because the concepts that you can learn from it.

Coding

Writing solid codeCode completeProgramming Pearls, more programming pearls(recommended)[NEW] Introduction to Algorithms

Programming

Refactoring (M. Fowler)Pragmatic ProgrammerClean code[NEW] Software Engineering: A Practitioner's Approach[NEW] The Mythical Man-Month[NEW] The Art of Computer Programming

Design

Applying UML and Patterns (GRASP patterns)C++ coding standards (Sutter, Alexandrescu)The C++ programming language (Stroustrup, Part IV)Object-oriented programming (Peter Coad)P…