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

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP