How dispatcher cache flush works for cached content with selector in AEM CS(Cloud Service)?

[Umesh_Thakur]

Hi Team,

Caching content with selector is common practice in AEM sites. Before AEM CS we were useing acs dispatcher flush rules to flush the cache of cached content with selector but in AEM CS it seems to be working by default means there is no need to have any custom mechanism to flush the content with selector in dispatcher. 

Is anyone is having any idea how cache flush works for content with selector in AEM CS dispatcher?

Thanks 

Umesh Thakur

[daniel-strmecki · Accepted solution]

Hi @Umesh_Thakur,

the page publication event triggers a flush that deletes the Dispatcher cache for the specific page, this includes any cached versions with selectors. You can verify this using AEM SDK and local Dispatcher.

Hope this helps,

Daniel

[Umesh_Thakur]

Thanks for your response @daniel-strmecki . It helps

[arunpatidar]

Hi @Umesh_Thakur 

As @daniel-strmecki  mentioned, When you publish a page or resource, the cache is cleared for all the files matching the resource path.

For example, if you publish /content/myapp/us/en, the cache will be invalidated for all versions of that resource, including:

• /content/myapp/us/en
• /content/myapp/us/en.html
• /content/myapp/us/en.json
• /content/myapp/us/en.my.json
• etc.

It works for all the AEM types i.e. AEMaaCS as well as AMS

[Umesh_Thakur]

Thank you for clarifying in detail @arunpatidar.