Hello llyas,

(system.webServer/staticContent/clientCache is for static resources (files))

you can create your own implementation of CachedPartial, something like this:

using System;
using System.Web.Mvc;
using System.Web.Mvc.Html;
using Umbraco.Web;
using System.Web;
using System.Runtime.Caching;

public static class CachedPartialExtensions
{
//(From version 7 there is an overload for CachedPartial that allows the key to be passed in)
public static IHtmlString CachedPartial(
this HtmlHelper htmlHelper,
string partialViewName,
object model,
int cachedSeconds,
bool cacheByPage = false,
bool cacheByMember = false,
ViewDataDictionary viewData = null,
Func<object, ViewDataDictionary, string> contextualKeyBuilder = null);
{
var newCacheKey = "fpc-"; //prefix to know which keys to clear on page publish (in Bootstraper.cs file)
newCacheKey += partialViewName;
if (cacheByPage)
{
newCacheKey += "page-" + UmbracoContext.Current.PageId;
}
if (!string.IsNullOrEmpty(cacheKey))
{
newCacheKey += "key-" + cacheKey;
}

var result = MemoryCache.Default.Get(newCacheKey) as MvcHtmlString;
if(result == null)
{
result = htmlHelper.Partial(partialViewName, model, viewData);
MemoryCache.Default.Add(new CacheItem(newCacheKey, result), new CacheItemPolicy
{
AbsoluteExpiration = DateTimeOffset.Now.AddSeconds(cachedSeconds)
});
}

return result;
}
}

The use case for this would be:

@Html.CachedPartial(
"PartialView",
MyModel3,
3600,
cacheByPage: true,
contextualKeyBuilder: (model, viewData) =>
{
return (model as MyViewModel).Id.ToString();
});

you will be able to provide your own keys for cache:

@Html.MyCachedPartial("PartialView", Model, 60, cacheKey: "model1key", cacheByPage: true)
@Html.MyCachedPartial("PartialView", Model2, 60, cacheKey: "model2key", cacheByPage: true)

Try to use Client side caching Easy way to add client side caching to site - add this section to your Web.config:

<location path="media">
<system.webServer>
<staticContent>
<clientCache cacheControlMode="UseMaxAge" cacheControlCustom="public" cacheControlMaxAge="7.00:00:00" />
</staticContent>
</system.webServer>
</location>

(For example, cache-control: max-age=120 means that the returned resource is valid for 120 seconds, after which the browser has to request a newer version)

is working on a reply...