More in this section

Forums / Developing with Sitefinity / Page Cache Synchronization Problem

Page Cache Synchronization Problem

5 posts, 0 answered
  1. Jacques
    Jacques avatar
    427 posts
    Registered:
    28 Jun 2007
    13 Apr 2010
    Link to this post
    We need to understand something about Sitefinity and caching a little better because:

    We have dual Windows 2003 servers hosting Sitefinity 3.7 SP3 both using the same Oracle 10g DB.
    Our caching is configured as follows.
    <caching defaultProvider="memoryCache">
       <providers>
         <add name="memoryCache" type="Telerik.Caching.MemoryCachingProvider, Telerik.Framework" />
         <add name="ASPNET" type="Telerik.Caching.AspNetCachingProvider, Telerik.Framework" duration="960" slidingExpiration="true" />
       </providers>
       <cacheDependency mode="InDatabase" />
     </caching>

    Our CacheDependency is set to InDatabase.

    On our front page we have a RadRotator actings as a news ticker. Since the upgrade we noticed a RadTicker that's available, but we're not sure whether it will support our layout of things (including title, intro, thumbnail, article # x of y), so we chose to stick with the rotator for the moment.

    So if the CMS editor adds a new "News" article and publishes it we expect to see the article in the news ticker immediately. The problem is that it appears and then you go to another page and back again and it's gone. So we assume it's different servers in the NLB cluster responding, but one of them is not updating the home page.

    Why would this be the case? What I understood from the Telerik team is that if content for the home page is change in the CMS then the cache is invalidated. But this is not entirely the case here since the changes are being made to the News Module, the home page just has to pick up the new article, which is happening on one server but not the other.

    Help!

    Jacques
  2. Jacques
    Jacques avatar
    427 posts
    Registered:
    28 Jun 2007
    13 Apr 2010
    Link to this post
    My thinking now is that the problem lies with the cache not being invalidated!

    Is there any way to invalidate the Home page cache when either:
    1. News articles are changed/added/removed or,
    2. Pages are changed/added/removed

    ?
    Jacques
  3. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    12 Sep 2017
    13 Apr 2010
    Link to this post
    Hi J.Hoventer,

    Have you tried to use CacheSubstitutionControl? This will allow you  to inject HTML into already cached output at predefined points. The ticker you have needs frequent updates. The HttpResponseSubstitutionCallback will allow you to register the predefined point with the response output.

    Sincerely yours,
    Ivan Dimitrov
    the Telerik team

    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
  4. Jacques
    Jacques avatar
    427 posts
    Registered:
    28 Jun 2007
    14 Apr 2010
    Link to this post
    Hi Ivan,

    I'm not sure what you're referring to. Can you give me a brief example or point me to an existing example?

    Thanks,
    Jacques
  5. Jacques
    Jacques avatar
    427 posts
    Registered:
    28 Jun 2007
    14 Apr 2010
    Link to this post
    Hi Ivan,

    I've just double checked the Substitution Control and its purpose. It returns a string value and I'm not sure what or when it gets triggered, but this does not seem like the obvious choice and solution to my problem.

    This is being used for a 'news ticker' (RadRotator) that is built in a user control. We can opt for partial caching with the control, but this seems to degrade the level of caching that can be done.

    The problem also exists when we create a normal link to a new page that was created. So we create a page in the CMS and we then create a link to that new page on the home page. When we keep refreshing, one of the servers responds with the home page showing the new link the other server responds with no link being shown, so clearly it's still responding out of cache. But my thought here was that Sitefinity would invalidate the cache????

    Jacques
Register for webinar
5 posts, 0 answered