[MGNLSTK-786] far future cache: use a more resource friendly pattern? Created: 03/Aug/11  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: base system
Affects Version/s: None
Fix Version/s: 1.5

Type: Improvement Priority: Neutral
Reporter: Philipp Bärfuss Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-3297 browser caching: make it configurable... Closed
is related to MGNLSTK-714 resources: use modification date to a... Closed
is related to MAGNOLIA-4520 farFutureCaching and Resource files w... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

We originally got inspired by the GWT approach of using a .timestamp.cache. pattern. But this has the following disadvantages:

  • the filename changes: if one loads js script dynamically one has no clue what the correct pattern would be
  • relative CSS resources (for instance background images) are not having a cache friendly filename

Solutions:
A) process the css file and add the timestamp dynamically if needed
+ doable as the files can be freemarker templates (processed CSS)
- how to know the correct modification date? in case the files are in the DMS?
- can be very complex

B) use a path prefix: /cache/timestamp/
+ filename doesn't change
+ relative resources are also cached
- only works for files which share the parent path (relative urls)
- the timestamp is shared. if one changes an image one has to touch the CSS file to change its modification date



 Comments   
Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 07:30:24 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.