Skip to main content

Data Sharing Across Threads in .Net



Namespace: System.Threading

Avoiding Collisions:
                Collision may occur while accessing data from multiple threads. Two threads loaded the same value, updated and set the value at the same time, and leaving the data in inconsistent state. Interlocked class can perform the arithmetic operations as single a single operation. These arithmetic operations include: Add, Decrement, Exchange, Increment, and Read operations.

Synchronization Locks:

C# lock can be used to make single thread enter the specified code at one time. Like:

                lock (this Or any Object)
                {
                }

It’s an object base lock. We will face a deadlock, if lock is not been released for others.

Monitor class is used behind the lock. Monitor class has the methods like Enter, Exit, TryEnter, and Wailt. TryEnter can be used with some timeout to avoid deadlock.

Lock and Monitor does not work across appDomain.

ReaderWriterLock can be used to attain read or write access to certain resource separately. Multiple readers can read at one time. But only one reader is allowed at a time. Important properties include IsReaderLockHeld and IsWriterLockHeld.

AcquireReaderLock, AcquireWriterLock, DownGradeFromWriterLock, and RealeaseReaderLock, RealeaseWriterLock, UpgradeToWriterLock are important methods.

Synchronization Lock: With windows kernel object.

Mutex: Mutex allows you to synchronize threads across AppDomains and Process boundaries. Mutex inherits from WaitHandle class. Single property Handle and methods are Close () and WaitOne().

Mutext m = new Mutex();
If( m.WaitOne(1000,false) )                         //wait for a second
{
}
finally
{
                m.ReleaseMutex();
}

OR

Try
{              m = Mutext.OpenExisintg(“ExistingMutexName”);     }
catch(Exception)
{}

if( m== null )
{
                m = new Mutext(false, “ExistingMutexName”);
}

Semaphore:
It provides kernel level some valid slot against a resource and block access until a slot is available.

Semaphore s = new Semaphore(0,10);
s.Release(5); // Release 5 slots.

Or

Try
{              s = Semaphore.OpenExisting(“s”);        }
Catch(Exception e)
{       s = new Semaphore(0, 10, “S” );           }

Event Class:
To signal threads across AppDomain and Process boundaries use Event class. This kernel level object has state on or off. Event types include AutoResetEvent and ManualResetEvent which inherit from EventWaitHandle which inherit from WaitHandle.

(AutoResetEvent, ManualResetEvent) → EventWaitHandle → WaitHandle

AutoResetEvent ar = new AutoResetEvent(true);
ManualReset mr = new ManualResetEvent(false);

Ar.Set();
Mr.Reset();

OR

EventWaitHandle awh = null;
Try{
Awh = EventWaitHandle.OpenExisting(“AWH”);
}
Catch() {}

If(awh == null)
{
                awh = new EventWaitHandle(false, EventResetMode.AutoReset, “AWH”);
}
Labels:

Comments

Post a Comment

Popular posts from this blog

Culture Information and Localization in .NET

Namespace: System.Globalization CultureInfo Class:                 It provides information like the Format of numbers and dates, Culture’s Calendar, Culture’s language and sublanguage (if applicable), Country and region of the culture. The Basic use of CultureInfo class is shown here: • How string Comparisons are performed • How Number Comparison & Formats are performed • Date Comparison and Formats. • How resources are retrieved and used. Cultures are grouped into three categories: Invariant Culture : It’s Culture Insensitive. It can be used to build some trial application. It can be also used to build an application with hard-coded expiry date that ignores cultures. But using it for every comparison will be incorrect and inappropriate. Neutral Culture : English(en), Frensh(fr), and Spanish(sp). A neutral culture is related to language but it’s not related to specific regi...
Post a Comment
Continue Reading »

Concept of App Domain in .Net

Creating Application Domains: Application domain is just like process, provides separate memory space, and isolates from other code. But it’s quite light weight. It also provides the following advantages: 1-       Reliability : If a domain crashes, it can be unloaded. Hence doesn’t affect the other assemblies. 2-       Efficiency : Loading all assemblies in one domain can be cumbersome and can make the process heavy but Appdomains are efficient in this manner. Important properties of AppDomain: ApplicationIdentity , ApplicationTrust , BaseDirectory , CurrentDomain , DomainManager , DomainDirectory , Evidence , FriendlyName , ID , RelativeSearchPath , SetupInformation , ShadowCopyFiles . Important methods of AppDomain: ApplyPolicy , CreateCOMInstanceFrom , CreateDomain , CreateInstance (Assembly). To create an AppDomain: AppDomain adomain = AppDomain.CreateDomain(“D”); To execute an assembly:...
Post a Comment
Continue Reading »

Asynchronous Execution in ASP.NET

Asynchronous Execution: Two ways either implement IHTTPAsyncHandler interface or in ASP.NET 2.0 set <%@ Page Async=”true” %>. The second option implements IHTTPAsyncHandler interface automatically for the page when parsed or compiled. AddOnPreRenderCompleteAsync ( new BeginEventHandler(BeginTask), new EndEventHandler(EndTask)); AddOnPreRenderCompleteAsync() shoud be called in Page_load. The BeginEventHandler and EndEventHandler are delegates defined as follows: IAsyncResult BeginEventHandler( object sender, EventArgs e, AsyncCallback cb, object state) void EndEventHandler( IAsyncResult ar) AsyncProcess starts and completes between PreRender and PreRenderComplete. Other way to perform Async Task is using AsyncPageTask structure. It also allows multiple tasks to execute simultaneously. void Page_Load (object sender, EventArgs e) { PageAsyncTask task = new PageAsyncTask( new BeginEventHandler(BeginTask), new EndEventH...
Continue Reading »