Hi，

manighht

if the same default.aspx page has to be stored in-proc or on the hard disk.

I don't understand why you may stored the cached page on the hard disk, maybe you just give a sample to explain how to chang the cache provider. If you cache the page on the hard dick, still need to use IO to read it, that may hit the performance.

manighht

What I'm missing is how to set those parameters programmatically (at run time if you prefer) and not in a declarative way.

You can surely change the parameters programmatically like this:

Response.Cache.SetExpires(DateTime.Now.AddSeconds(60));
Response.Cache.SetCacheability(HttpCacheability.Public);
Response.Cache.SetValidUntilExpires(true);

http://msdn.microsoft.com/en-us/library/z852zf6b.aspx

manighht

This is a granular way of adjusting some caching parameters based on admin preferences, wich on turn are based on website traffic or specific pages traffic and so on

I'm afraid you can't implement this functionality currently. If you host your web application on IIS, you also can via the output cacheing of IIS to configure your web application anytime.