sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Munteanu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SLING-7964) Make the suffix optional for included resources
Date Fri, 26 Oct 2018 14:28:00 GMT

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

Robert Munteanu updated SLING-7964:
-----------------------------------
    Fix Version/s: Dynamic Include 3.1.4

> Make the suffix optional for included resources
> -----------------------------------------------
>
>                 Key: SLING-7964
>                 URL: https://issues.apache.org/jira/browse/SLING-7964
>             Project: Sling
>          Issue Type: Improvement
>    Affects Versions: Dynamic Include 3.1.2
>            Reporter: John Mitchell
>            Priority: Minor
>             Fix For: Dynamic Include 3.1.4
>
>
> I'm using Sling Dynamic Includes to cache re-usable content for search results. That
is to say that the search results are dynamic - but the content of the individual results
are not.
> The structure of the page was that the original request from the browser had a suffix
to indicate the search query:
> {code:java}
> /path/to/search/results/page.html/query/for/the/search{code}
> The search results were inserted using non-synthetic page resources and a included selector
to render a specific form of that page. The problem was that the original suffix of the parent
request was included in the SSI include - so that there were numerous versions of the child
resource, and therefore didn't achieve the cache hit ratio we were looking for.
> This PR adds a new option that makes this optional (current behaviour maintained by default)
- so that this "reverse" dynamic include use case is catered for.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message