If I attach an event handler to PageCacheRefresher.CacheUpdated does that run at all times regardless of whether you are using flexible load balancing or not?
It's running in my local install too which is a single SQL Express db test site. This means events can potentially be fired when binding to both PageCacheRefresher.CacheUpdated and ContentService.Published
The ContentService published event will only be fired on the server where the button is pushed. If you have a single instance this is okay.
But when you have a loadbalanced environment or when you have multiple contentservice published events it's better to use the PageCacheRefresher updated event. This will fire after all publishing events have been completed. And also will be called on all servers.
PageCacheRefresher.CacheUpdated
A quicky here,
If I attach an event handler to
PageCacheRefresher.CacheUpdateddoes that run at all times regardless of whether you are using flexible load balancing or not?It appears to.
Hi James,
It will always run. If you are using loadbalancing, flexible or traditional, this is the even you need to clear your own caches.
Dave
Thanks Dave.
It's running in my local install too which is a single SQL Express db test site. This means events can potentially be fired when binding to both
PageCacheRefresher.CacheUpdatedandContentService.PublishedI dunno if this is by design...
Hi James,
The ContentService published event will only be fired on the server where the button is pushed. If you have a single instance this is okay.
But when you have a loadbalanced environment or when you have multiple contentservice published events it's better to use the PageCacheRefresher updated event. This will fire after all publishing events have been completed. And also will be called on all servers.
Dave
Ah Dave,
That makes sense now. Much appreciated! :)
is working on a reply...