I was testing the various output caching methods including at the page level and module level.  I had remembered reading a post about saving an entire page in Pro Version, so I thought I would check it out.  After testing both page and module level caching I am left wondering what use it is for a majority of people.  The page level cache won't work for logged in users, there may be some limited number of websites that can really capitalize on this, but really, it's use seems extremely limited.  What it does have is some useful include/exclude parameter settings.  Onto module cache...it does cache for logged in users, but is limited to a module with static content regardless of querystring changes etc.  If only the module level cache had the include/exclude qs parameter settings that the page level cache did.  Would this not be 50X more useful than any of the existing caching possibilities?

I guess while I am posting in the performance section and just popped the image manager of this forum open to wait over a minute for it to attempt to load before finally closing it out, I will ask.  Is there any plans to get rid of the Telerik controls?  They are horribly slow bloated controls and it seems DNN is using more rather than less.  I don't understand this.  I know they do have some pros, but it seems vastly outweighed by the cons.

hmm, I think you missed my point.  Yes IIS 7 can be used but again, not for logged in users.  The module caching inside DNN is great for a content but cannot be used if the module content will vary.  If module cached content could vary based on something simple like url or something more advanced to accomodate things like AJAX requests it would just be so much more useful than any of the existing options.  With all the providers and options for both page and module level caching it has clear some significant work has been put in on caching, yet the result is still a very limited breadth of real world caching possibilities.  It would not take much to fix this.