You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Jörg Hoh (Jira)" <ji...@apache.org> on 2020/03/05 19:19:00 UTC

[jira] [Comment Edited] (SLING-9174) Add option to replace component path to experience fragment variation path

    [ https://issues.apache.org/jira/browse/SLING-9174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17052441#comment-17052441 ] 

Jörg Hoh edited comment on SLING-9174 at 3/5/20, 7:18 PM:
----------------------------------------------------------

[~kmittal] can you please explain the change you are about to make without referring to the terms of AEM? I don't think everyone is familiar with them, and it makes the change more understandable. Also In the PR there are a few occurrences of these terms.

Thanks!


was (Author: joerghoh):
[~kmittal] can you please explain the change you are about to make without referring to the terms of AEM? I don't think everyone is familiar with them, and it makes the change more understandable. 

Thanks!

> 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: DynamicInclude-Cache.png
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> 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:
> !DynamicInclude-Cache.png|width=1246,height=772!
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)