>>>>I do not know the specific answer to your question, but I use www.master.com watchdog feature to 1 - keep the site alive and 2 - to report to me if it goes down.
>>>
>>>There is no problem with the site. What I am trying to explain here is the sleep mode that IIS goes into if no activity is on the site. But, the site responds. It is just that when a hit will arrive, after a period of no activity, it will take longer for IIS to start responding such as 3 to 4 second instead of 0.2.
>>
>>master.com watchdog can hit the site every 15 minutes, keeping it alive so it does not take 3-4 seconds, provided it is visible to master.com
>
>I assume that just stops the idle timeout from kicking in? From what Michel has said it doesn't sound as if that is what's causing the re-cycling in this instance ?

It sounds to me like his IIS timeout is kicking in because he hasn't worked on the development site for over an hour. The 20 minute timeout happens, unless the site gets a hit. That's my understanding, but please tell me if that's not so. I'm doing my development on a remote host and if there is another way to keep it live, I'd like to know it too. I think the remote host will not let me alter IIS though. So I found master.com and told it to hit my site's KeepAlive.aspx every 15 minutes. Seems to be working for me. So I offered it as a suggestion in case our situations are similar. :)

Mike