I'm creating an application with a <code>NetTcpBinding</code> service and a <code>BasicHttpBinding</code> one. Through these services, the clients send requests to the application: these requests must be put into a <code>Queue</code> object, that is the queue of inbound request. <ol> <li>Both services must allow concurrent calls from the clients.</li> <li>This means that both services should access concurrently to the queue in order to add the received requests.</li> <li>In addition, another thread must access the queue in order to get and process the requests.</li> </ol> I could use <code>ConcurrencyMode.Multiple</code> and so many calls could be taken simultaneously. However, this does not guarantee a concurrent access to the queue. Should I put the two <code>ServiceHost</code> in two different thread? For example: <ul> <li>The first thread dequeues and processes the requests in the queue.</li> <li>The second thread instantiates the <code>NetTcpBinding</code> service and enqueues new requests in the queue. Moreover, it sends any replies via callback.</li> <li>The third thread instantiates the <code>BasicHttpBinding</code> service and enqueues new requests in the queue.</li> </ul> This is my idea. Since I am almost a newbie, I would be grateful if you could give me some advice. Maybe I should start writing three threads that access the queue concurrently: for the moment the first two threads may enqueue random requests to the queue, while the third thread consume these requests.

IF you are on .NET 4 you should look into <code>ConcurrentQueue<T></code> and <code>BlockingCollection</code>. Bascially these are thread-safe collections which are implemented for high performance and are mostly lock-free. <code>BlockingCollection</code> is specifically implemented for Producer-Consumer-Scenarios like the one you describe. For reference see: <ul> <li>http://msdn.microsoft.com/en-us/library/dd267265.aspx</li> <li>http://geekswithblogs.net/BlackRabbitCoder/archive/2011/02/10/c.net-little-wonders-the-concurrent-collections-1-of-3.aspx</li> <li>http://msdn.microsoft.com/en-us/library/dd997371.aspx</li> <li>http://blogs.msdn.com/b/csharpfaq/archive/2010/08/12/blocking-collection-and-the-producer-consumer-problem.aspx</li> <li>http://msdn.microsoft.com/en-us/library/dd267312.aspx</li> </ul>

Concurrent access to a queue by multiple threads

I'm creating an application with a NetTcpBinding service and a BasicHttpBinding one. Through these services, the clients send requests to the application: these requests must be put into a Queue object, that is the queue of inbound request.

Both services must allow concurrent calls from the clients.
This means that both services should access concurrently to the queue in order to add the received requests.
In addition, another thread must access the queue in order to get and process the requests.

I could use ConcurrencyMode.Multiple and so many calls could be taken simultaneously. However, this does not guarantee a concurrent access to the queue. Should I put the two ServiceHost in two different thread? For example:

The first thread dequeues and processes the requests in the queue.
The second thread instantiates the NetTcpBinding service and enqueues new requests in the queue. Moreover, it sends any replies via callback.
The third thread instantiates the BasicHttpBinding service and enqueues new requests in the queue.

This is my idea. Since I am almost a newbie, I would be grateful if you could give me some advice. Maybe I should start writing three threads that access the queue concurrently: for the moment the first two threads may enqueue random requests to the queue, while the third thread consume these requests.

What is concurrent queue?

A concurrent queue is basically a queue which provides protection against multiple threads mutating its state and thus causing inconsistencies. A naive way to implement a concurrent queue may be to just slap locks in its enqueue and dequeue functions when they try to modify the head and tail.

Is concurrent queue thread-safe?

ConcurrentQueue is a thread-safe FIFO data structure. It's a specialized data structure and can be used in cases when we want to process data in a First In First Out manner.

Can you explain how IOS supports multi threading?

Multithreading is an implementation handled by the host operating system to allow the creation and usage of n amount of threads. Its main purpose is to provide simultaneous execution of two or more parts of a program to utilize all available CPU time.

What is difference between thread and queue?

A message queue is a data structure for holding messages from the time they're sent until the time the receiver retrieves and acts on them. Generally queues are used as a way to 'connect' producers (of data) & consumers (of data). A thread pool is a pool of threads that do some sort of processing.

IF you are on .NET 4 you should look into ConcurrentQueue<T> and BlockingCollection.

Bascially these are thread-safe collections which are implemented for high performance and are mostly lock-free.

BlockingCollection is specifically implemented for Producer-Consumer-Scenarios like the one you describe.

For reference see:

http://msdn.microsoft.com/en-us/library/dd267265.aspx
http://geekswithblogs.net/BlackRabbitCoder/archive/2011/02/10/c.net-little-wonders-the-concurrent-collections-1-of-3.aspx
http://msdn.microsoft.com/en-us/library/dd997371.aspx
http://blogs.msdn.com/b/csharpfaq/archive/2010/08/12/blocking-collection-and-the-producer-consumer-problem.aspx
http://msdn.microsoft.com/en-us/library/dd267312.aspx

Concurrent access to a queue by multiple threads

Tags:

c#

.net

wcf

enzom83

People also ask

1 Answers

Yahia

Recent Activity

Donate For Us

Concurrent access to a queue by multiple threads

Tags:

c#

.net

wcf

enzom83

People also ask

1 Answers

Yahia

Related questions

Recent Activity

Donate For Us