Dispatcher cache invalidation

[selvaganesh]

I have the dispatcher configured to point publish. Whenever I am publishing a page , the dispatcher invalidates the cache . I don't want the dispatcher to delete the cache immediately. I commented /invalidate , but still it is deleting the cache file.

[Pawan-Gupta]

Did you configure and enabled "Dispatcher flush agent" on publish replication agent?? because that agent is also responsible to trigger the flush on dispatcher based on configured event.

[Jörg_Hoh · Accepted solution]

Hi,

How do you want to the dispatcher to actually get the old data out of the cache? What's the stragey you would like ot have?

Kind regards,
Jörg

[selvaganesh]

I am making http access calls to dispatcher  so that that dispatcher cache is made ready with new data during the publishing stage itself. Since dispatcher is invalidating it , the html files made by http access also gets deleted.

[Jörg_Hoh]

Hi,

so you are concerned about the fact, that files need to refetched from publish first and then being delivered to the browser? I think, that's the price you need to pay to fill up any cache ...

If you can live with stale data, you can omit the invalidation on a change, and rather invalidate time-base (using simply cron). After that you can start another script to fill the cache again.

kind regards,
Jörg