multithreading - Practices for Foreground/Background threads in .NET -
i work in-house legacy communication framework exposes high level abstractions. these abstractions wrappers logic around .net threads. when looked @ code i've noticed abstractions wrappers around foreground threads while others wrappers around background threads.
the sad thing don't see logic why in cases foreground threads used , background in other cases.
are there guidelines or patterns & practices when it's better choose 1 on on server side , client side (i believe there should difference)?
any examples own professional experience when crucial or solution prefer 1 on another?
straight msdn
a managed thread either background thread or foreground thread. background threads identical foreground threads 1 exception: background thread not keep managed execution environment running. once foreground threads have been stopped in managed process (where .exe file managed assembly), system stops background threads , shuts down.
Comments
Post a Comment