Skip to main content

Callback in c#


Download


Running tasks in background is the need of the hour when working on real world applications. There are few tasks which we can fire and forget but for few of them we will like to receive the feedback. This is when callbacks comes into the picture and provides a channel for these objects to communicate with each other.

These tasks are very common in desktop and mobile applications. In this post we will talk about callback mechanism in c#. In future post we will build upon this and do lot more.

Using interfaces for callbacks in c#


using System;
using System.Threading;

namespace Callbacks
{
    
    class Program
    {
        static void Main(string[] args)
        {
            var consumer = new Consumer();
            consumer.DoWork();
            Console.ReadLine();
        }
    }

    interface IOnProcessCompleteListener
    {
        void OnProcessComplete(string message);
    }

    internal class Consumer: IOnProcessCompleteListener
    {
        private Worker _worker;
        public Consumer()
        {
            _worker = new Worker();
            _worker.OnProcessCompleteListener = this;
        }

        public void DoWork()
        {
            Thread backgroundThread = new Thread(_worker.DoBackgroundWork);
            backgroundThread.Start();
            Console.WriteLine("Control is with main thread");
        }

        public void OnProcessComplete(string message)
        {
            Console.WriteLine(message);
        }
    }
    internal class Worker
    {
        public IOnProcessCompleteListener OnProcessCompleteListener;

        public void DoBackgroundWork()
        {
            Console.WriteLine("In worker");
            Thread.Sleep(1000);

            if(OnProcessCompleteListener != null)
                OnProcessCompleteListener.OnProcessComplete("Consumer has been called back");
        }

    }
}


Code is self explanatory and thus I will provide just a brief on it. We created an interface IOnProcessCompleteListener it has just one method. In the Worker class we have an data member which accepts an object of class which implements IOnProcessCompleteListener. This ensures that we can call OnProcessComplete method on this member once we are ready to call it back. The Consumer class will implement IOnPropertyChangeListener. Once Worker is done with stuff it will notify Consumer using the callback object. Just to simulate some background process I have made the worker thread to sleep before giving the call back.

Using Delegates to callback in c#


using System;
using System.Threading;

namespace CallBacksUsingDelegate
{
    class Program
    {
        static void Main(string[] args)
        {

            Listener listener = new Listener();
            listener.DoWork();
            Console.WriteLine("Now in main thread");
            Console.ReadLine();
        }
    }

    internal delegate void OnProcessComplete(string message);

    internal class Worker
    {
        public OnProcessComplete ProcessComplete;

        public void Process()
        {
            Console.WriteLine("Process: Running on " + Thread.CurrentThread.Name);
            Thread.Sleep(1000);
            if (ProcessComplete != null)
                ProcessComplete.Invoke("Process has completed");
        }
    }

    internal class Listener
    {
        private Worker _worker;
        public Listener()
        {
            _worker = new Worker();
            _worker.ProcessComplete = this.ProcessCompleteListener;
        }

        public void DoWork()
        {
            Thread backgroundThread = new Thread(_worker.Process);
            backgroundThread.Name = "Background Thread";
            backgroundThread.Start();
        }

        private void ProcessCompleteListener(string message)
        {
            Console.WriteLine(message);
        }
    }

}

In this case we have a delegate - OnProcessComplete. Class worker has an object of type OnProcessComplete and class Listener passes the callback function to the Worker wrapped in this delegate. Once the Worker is done with its stuff it invokes the delegate and passes the control back.

In the coming posts we will explore this power a bit more and try to do something more meaningful.

Your inputs are really important for me so please do provide them. Share it if you care :)

Comments

  1. Nice explanation of callbacks and its comparison with C#'s concept of delegates is awesome.

    ReplyDelete

Post a Comment

Popular posts from this blog

Laravel XAMPP MySQL artisan migrate install error mysql.sock

In my previous post I wrote about setting up Laravel 4 on Mac with XAMPP . When I tried to use migrations (using artisan) I faced some issue. I will also post about Laravel migrations soon.    php artisan migrate:install Error :                                                     [PDOException]                                       SQLSTATE[HY000] [2002] No such file or directory                                              Solution : We need to tell artisan which mysql we want it to use. For this to work we need to porivde it with mysql.sock which we want it to use. So change your database settings like this: 'mysql' => array( 'driver'    => 'mysql', 'host'      => 'localhost',     'unix_socket' => '/Applications/xampp/xamppfiles/var/mysql/mysql.sock', 'database'  => 'wedding', 'username'  => 'root', 'password'  => '', '

Add (Drop) a new article (table) at publisher in merge replication

Let us add the article using the GUI first. First of all create the table on publisher database. Now right click on the publisher and select properties from the menu. Click on articles. Uncheck the - "Show only checked articles in the list" checkbox, in order to see the newly added table. Select the table as shown in the figure below. Press ok The article has now been added to the publisher We now need to recreate the snapshot Right click the publication and select – “View snapshot agent status”. Click start to regenerate snapshot. Now right click on the subscription (I have both on same server you may have on different servers) and select “View synchronization status” Click on start on the agent. The schema changes will propagate to the client if you have "Replicate schema changes" property set to true in the publisher.

Check SQL Server Job status (State) using sp_help_job and xp_sqlagent_enum_jobs

This article is about checking the status of a SQL job. In our work place we have lot of SQL jobs. These jobs will run whole day and are business critical. They will load the data and generate extracts which will be used by business people. Thus, it becomes quite essential to support the system efficiently so that the job finishes in time and as desired. Also, while designing a new system sometimes we need to check the dependency of one job over another. In such scenario we need to check whether a particular job has finished or not. All this can be achieved in SQL Server by using the procedures:- sp_help_job xp_sqlagent_enum_jobs Note: xp_sqlagent_enum_jobs is an undocumented proc inside of sp_help_job and is used extensively to get SQL agent job information. sp_help_job: This procedure gives some insight into the status, and information, about a job. This stored procedure provides information such as last start time, job status etc. Syntax sp_help_job { [ @job_id= ] jo