sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Van Geem (JIRA)" <>
Subject [jira] [Commented] (SLING-7914) Document the way synthetic resources can be cached with the right SDI config
Date Mon, 20 May 2019 20:25:00 GMT


Eric Van Geem commented on SLING-7914:

I believe there is a bug with setting a TTL on synthetic resources since I was not able to
get it working with SDI v3.1.2. I have opened a separate issue for this as well as a Github
PR with a fix.

> Document the way synthetic resources can be cached with the right SDI config
> ----------------------------------------------------------------------------
>                 Key: SLING-7914
>                 URL:
>             Project: Sling
>          Issue Type: Wish
>    Affects Versions: Dynamic Include 3.1.2
>            Reporter: Tomasz Niedźwiedź
>            Priority: Minor
> SLING-7785 introduced a way for components based on virtual resources to be cached.
A new property was added to the configuration which allows a faux extension to be appended
to the suffix, enabling the content to be cached and a TTL to be respected.
> I've recently come across a [Stack Overflow question|] that
seems related to the improvement introduced there but, spending time to experimenting with
it myself, I'm not sure how exactly the feature needs to be configured. Please consider writing
a few paragraphs describing the use of this feature on the [SDI documentation page|].
> What I think would work nicely would be to:
>  * Add the _Extension_ property to the list of configurable fields and provide a brief
>  * Provide an example of a minimal SDI and Dispatcher configuration to cache a synthetic
resource with a specific TTL.
> For anyone who wants to pick this up, the markdown for this exact page can be found [here|].
> CC [~AndreasWurm]

This message was sent by Atlassian JIRA

View raw message