Multithreading in C#

Question

1.00/5 (1 vote)

See more:

Hi Good Morning!

I'm building an application that Read the XML from SQL table and then processes it and write in to text file

I Have two method ReadXML() which read XML file & returning Business Entity object.
second method WriteXML() which takes Business Entity object and write into text file.

Here's how I want it to operate:

In main thread I want to create two thread one is for ReadXML() which will read XML & return Business Entity object which I have to store in Queue & second thread for WriteXML() which will read object from queue & write into text file.

How can I implement such a scenario? Queue will be shared by two threads?
How that queuing will be done?

- Dattatrya Moin

Posted 2-Apr-12 16:56pm

Dattatrya Moin 11

Updated 2-Apr-12 18:14pm

v2

Add a Solution

Comments

Sergey Alexandrovich Kryukov 2-Apr-12 23:36pm

Well... of cause you can do it with threads, the questions are: why? is reading or writing of XML supposed to take so long time? and what is the problem?
--SA

Dattatrya Moin 11 3-Apr-12 0:17am

Problem is How to share the queue between two threads? And What kind of care should I take. If you know best link to read about this please share..

Thanks.

Sergey Alexandrovich Kryukov 3-Apr-12 1:32am

lock {/*...*/}

--SA

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Accepted Answer · 2012-04-02T19:49:00

Let's assume you are using System.Collections.Generic.Queue<T>. Please see:
http://msdn.microsoft.com/en-us/library/7977ey2c.aspx[^].

Read the section "Thread Safety". It explains what exactly you should do. You must implement your own synchronization. Practically, simply wrap the operations you need with lock, for example:

C#

internal class QueueWrapper<T> {
    internal void void Enqueue(T item) {
        lock(SyncObject)
            Implementation.Enqueue(item);
    }
    internal T Dequeue() {
        lock(SyncObject)
            return Implementation.Dequeue();
    }
    System.Collections.Generic.Queue<T> Implementation =
        new System.Collections.Generic.Queue<T>();
    object SyncObject = new Object(); // always lock with a private object, see below
}

Don't do lock(this); it would work but allow outside lock with the QueueWrapper instance. So, hiding the synchronization object SyncObject inside wrapper is a good fool-proof technique: no one will be able to create excessive synchronization with such object and compromise parallelism.

—SA