I would probably ask if this is a problem that needs to be solved first. Changing localization texts is a rare occurence and if the old text is shown a couple of minutes because it's cached is normally not a real issue. If it really is, of course cache time can be lowered to reduce the problem. If it's critical but very rare you can manually purge cache on frontend nodes when doing a big deploy etc. If it's critical and very common I would get those localized values by javascript api instead. I know there is a good built in api for Valdis localization provider (I'm using it myself in SPAs). 

Trying to build some advanced cache purge push hierarchy I would stay away from. It will likely generate more errors than it solves.

Happy coding and good luck!

Hi Daniel,

I am planning to use Valdis localization provider too.

Are you talking about whole website cache purging?. Currently we purge cache for a specific page lets say when page gets newly published (by hooking an event while publishing). I want to do the similar kind of solution, but with localization the problem is:

a. Valdis provider is an nuget package, so I am not sure how much it is extendable for hooking an event so that when editor makes changes to localization text, it can reflect on the pages it affects.

2. A single Localization text can be used on mulitple pages, so, all the pages which are using the updated text by editor should be purged cache.

I am not sure by hooking an event or something how can we purge those specific set of website pages.

//Sanket Mahimkar