You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (Jira)" <ji...@apache.org> on 2022/01/11 13:44:00 UTC

[jira] [Updated] (SLING-8693) Additional support for Anonymous v/s loggedin user experiences

     [ https://issues.apache.org/jira/browse/SLING-8693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Munteanu updated SLING-8693:
-----------------------------------
    Fix Version/s: Dynamic Include 3.3.2
                       (was: Dynamic Include 3.3.0)

> Additional support for Anonymous v/s loggedin user experiences
> --------------------------------------------------------------
>
>                 Key: SLING-8693
>                 URL: https://issues.apache.org/jira/browse/SLING-8693
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Mayank Arora
>            Priority: Major
>             Fix For: Dynamic Include 3.3.2
>
>
> I am using SDI heavily for my current project but unable to achieve a usecase.  Not sure if this is currently a product gap or something not covered in documentation.
> Usecase is that there is a dynamic component on a page for which content is personalized per logged-in user and returned from an API. So, I have specified no-cache for this component (resource type) in SDI config.
> A variation of this usecase is if the User is not logged in, then all anonymous users see static/authored content for this component, which we want to cache. Traffic we are seeing is 50% anonymous v/s logged-in users, so there is a great benefit if we can cache static/authored content for this component for anonymous users. As per SDI configuration, I am unable to find a way where for this component (specific resourceType), using SSI, I can achieve no-cache for logged-in users v/s cache for anonymous users.
> Logging this as a feature request / documentation update request. Is this . usecase currently possible in SDI?



--
This message was sent by Atlassian Jira
(v8.20.1#820001)