[
https://issues.apache.org/jira/browse/SLING-9174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kunal Mittal updated SLING-9174:
--------------------------------
Attachment: (was: Screenshot 2020-03-05 at 13.26.46.png)
> Add option to replace component path to experience fragment variation path
> --------------------------------------------------------------------------
>
> Key: SLING-9174
> URL: https://issues.apache.org/jira/browse/SLING-9174
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: Dynamic Include 3.1.6
> Reporter: Kunal Mittal
> Priority: Major
> Attachments: SDI-Cache.png
>
>
> The SDI module currently includes the path of the component in the SSI
> directive which creates the cache under the page where the component is
> added.
> If we make use of Experience Fragment then rather than going to the
> Experience Fragment Core Component, the module can directly include the path
> of the XF variation. In case if we choose to cache it, then the cache is
> created at a single place rather than under each page.
> *Benefits*:
> # Performance
> ** Considerably reduces the number of calls to Publisher
> # Cache Optimization
> ** No custom code to invalidate cache entries created under every page
> *Current implementation*:
> {code:java}
> ## Directive added in the page after processing of SDI
> <!--#include
> virtual="/content/sdi/us/en/test-sdi/_jcr_content/root/responsivegrid/experiencefragment.nocache.html"
> -->
> {code}
> *Enhancement*:
> {code:java}
> ## Directive added in the page after processing of SDI
> <!--#include
> virtual="/content/experience-fragments/sdi/us/en/content/master.content.nocache.html"
> -->
> {code}
> Below are the differences when it comes to caching:
> !SDI-Cache.png|width=1373,height=707!
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
