1. Given the request was completed, how do we guarantee that the site won't spin down by IIS for long running command?  Don't we need to increment the busy count for IIS/ASP.NET?
2. Since the worker is no longer tied to request, we need to test if w3wp is down (spin down, killed, crashed), it should also terminate the worker exe as well (avoiding runnaway process).