Skip to main content

How to pass data to Thread - Part 2

Passing data to Thread using ParameterizedThreadStart  is the easiest way but not a type safe way as Thead.Start accepts any object.

Alternative way is to encapsulate Thread procedure and data in a helper class and use the ThreadStart delegate to execute the Thread procedure.

Make a note that you cannot return data from the Thread as there is no way to retrieve data from an asynchronous call. To retrieve data, you need callback method....which will look at part 3 of this article.

Here is an example on how to pass data in a type safe way

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading;

namespace ThreadTypeSafe
{
class Program
{
static void Main(string[] args)
{
TypeSafe ts = new TypeSafe(100, "This is message from a TypeSafe Thread with num as {0}");
Thread t1 = new Thread(ts.ThreadProc);
t1.Start();
t1.Join();
Console.WriteLine("Main thread exiting");
Console.ReadKey();
}
}

public class TypeSafe
{
private int _num;
private string _msg;

public TypeSafe(int num, string msg)
{
_num = num;
_msg = msg;
}

public void ThreadProc()
{
Console.WriteLine(_msg, _num);
}

}
}

Comments

Popular posts from this blog

Why there is semicolon at the start of a JavaScript function?

Very often while reviewing the code for my team, I will come across a semicolon at the start of JavaScript function as show below ; (function () { 'use strict'; ...and I often wondered what purpose it served. Guess what. It is an insurance to make sure your script works fine when all other scripts are merged together;  The leading ; in front of immediately-invoked function expressions (iffe) is there to prevent errors when appending the file during concatenation to a file containing an expression not properly terminated with a ;. So there you go. Now you know what that little semicolon is doing there in your code.

C# Performance Improvement - The Power of StringBuilder

 Often when we are wring code we don't think about performance and go with the default options available to achieve a task. String concatenation is one such scenario. If you are doing simple and few string catenations, then you can use the following result = string1 + string2; string1+= string2; result = String.Concat(string1,string2); String.Format and string interpolation are few other options.  However when you are performing large and repetitive  operation, string catenation can be expensive. Here is an example to prove the point.  As you can see it took 41 seconds to perform 100k string catenation. Now lets replace this with StringBuilder and see.  8 ms!!!!!! That is a massive performance difference. Hope you get the point. More info on StringBuilder can be found here https://learn.microsoft.com/en-us/dotnet/api/system.text.stringbuilder?view=net-7.0