Practices for Foreground/Background threads in .NET

Posted by Andrei Taptunov on Stack Overflow See other posts from Stack Overflow or by Andrei Taptunov
Published on 2011-02-28T14:30:06Z Indexed on 2011/02/28 15:24 UTC
Read the original article Hit count: 362

I work with in-house legacy communication framework which exposes some high level abstractions. These abstractions are wrappers with some logic around .NET threads. When I looked at code I've noticed that some abstractions are wrappers around foreground threads while others are wrappers around background threads.

The sad thing is that I don't see any logic why in some cases foreground threads are used and background in other cases.

Are there any guidelines or patterns & practices when it's better to choose one over another on server side and client side (I believe there should be some difference)?

© Stack Overflow or respective owner

Related posts about .NET

Related posts about multithreading