In my ASP.NET MVC application I have a number of threads that wait for a certain length of time and wake up to do some clean tasks over and over. I have not deployed this application to a production server yet but on my dev machine they seem to work as expected. For these threads to work the same on IIS7 do I need to look out for anything? Will IIS7 keep my threads alive indefinitely? are there implications to worry about?
Also I want to queue, lets say 50 objects that were created through various requests and process them all in one go. I’d like to maintain them inside a list and then process the list which means that the list object has to be kept alive indefinitely. I’d like to avoid serializing my objects into the DB in order to maintain this queue. What is the correct way of achieving this?
No, if the application pool recycles (if there’s a long inactivity or some memory threshold is hit) those threads will be stopped as the application will be unloaded from memory. If those objects are so much precise I wouldn’t recommend you keeping them in memory but rather serialize them to some persistent storage so that they could be processed later in case of failure.