Question

I have a situation where I have a polling thread for a TCPClient (is that the best plan for a discrete TCP device?) which aggregates messages and occasionally responds to those messages by firing off events. The event producer really doesn’t care much if the thread is blocked for a long time, but the consumer’s design is such that I’d prefer to have it invoke the handlers on a single worker thread that I’ve got for handling a state machine.

The question then is this. How should I best manage the creation, configuration (thread name, is background, etc.) lifetime, and marshaling of calls for these threads using the Task library? I’m somewhat familiar with doing this explicitly using the Thread type, but when at all possible my company prefers to do what we can just through the use of Task.

Edit: I believe what I need here will be based around a SynchronizationContext on the consumer’s type that ensures that tasks are schedules on a single thread tied to that context.

Answer 1

The question then is this. How should I best manage the creation, configuration (thread name, is background, etc.) lifetime, and marshaling of calls for these threads using the Task library?

This sounds like a perfect use case for BlockingCollection<T>. This class is designed specifically for producer/consumer scenarios, and allows you to have any threads add to the collection (which acts like a thread safe queue), and one (or more) thread or task call blockingCollection.GetConsumingEnumerable() to “consume” the items.