Hi John... I was just browing your snapsis forums to see if anyone was still experiencing the same issues as I was, and I found *exactly* the same thing/problem I was having:

http://www.snapsis.com/Support/SnapsisnbspSupport/tabid/601/forumid/9/postid/4626/view/topic/Default.aspx

And after getting to the bottom of the post, it looks like you were able to solve this issue and produced a new .dll.  I had the same exact issue, and we were at the stage where you were going to try to log onto my server to see what was going on... that's where we left off.  (here's my post: http://www.snapsis.com/Support/SnapsisnbspSupport/tabid/601/view/topic/forumid/9/postid/4385/Default.aspx) But it sounds like you've got it going now.  As you could tell from the poster, it was extremely frustrating to have to deal with content that wasn't being updated... visible while you were logged in, but as an anonymous user, the changes weren't visible... even after hitting CTRL+F5 300x in a row.  :)

Congrats on getting it fixed... I think your caching concept is wonderful, and would highly recommend it for those who are experiencing caching issues on servers where shared hosting is happening.

Take care,
Mike

There are really two issues here.  The first is the architecture of ASP.NET.  Pages are compiled on first request and cached for further requests.  If no request comes over a period of time, the cached page is dumped.  Also, if changes occur to the page code, and sometimes other files such as web.config, the page has to be recompiled due to a lost cache, session or app pool recycling.

The solution to this problem is a popular site where pages are frequently requested and thus stay in the cache.

The second problem is that DNN is a pig.  Because of what it's doing, the code takes longer to process.  This is especially true with less powerful SQL boxes, shared hosts and other situations where DNN is denied resources it wants.  The solution there is tuning DNN and SQL, even to stripping unwanted code, and using utilities such as PageBlaster to improve response time.

PHP is interpreted (for the most part) and doesn't use just in time compiling, so it can respond quicker.

Jeff

Hi Mitchel,

There are a lot of free monitoring applications already available on the internet. 
You may want to develop it yourself, but you might want to consider using one that has already been developed.

http://www.softplatz.com/freeware/host-monitor/