Are there any caveats or short comings to using the new Task API in S开发者_如何学Pythonystem.Threading.Task
in ASP.NET hosted under IIS?
I know prior to .NET 4.0 working with any of the ThreadPool actions inside of IIS was always recommended to be avoided.
Any caveats to using ThreadPool with IIS would still be valid using System.Threading.Task
, as the Task API is just an additional layer of abstraction over System.Threading
.
For long-running tasks in the background, I use a ThreadPool
inside a Windows Service. This keeps it outside of IIS.
精彩评论