[MAGNOLIA-5550] Allow dedicated caching of areas Created: 15/Dec/13  Updated: 19/May/22  Resolved: 19/May/22

Status: Closed
Project: Magnolia
Component/s: templating
Affects Version/s: 5.2
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Thomas Kratz [X] (Inactive) Assignee: Unassigned
Resolution: Won't Do Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

On some of our sites, we almost nowhere are able to rely on the caching system because of have dynamic elements on each page that cannot be captured by relying on the request based caching of magnolia. One approach that could truly speedup our rendering would be to allow dedicated caching of areas that are to be rendered, as most of the areas are static and only some of them have dynamic content. I think it would be not so hard to implement if you gave me a hint how I could create a custom areaTag that uses a custom AreaElement for rendering. I would be willing to provide my implementation as a prototype implementation.



 Comments   
Comment by Roman Kovařík [ 19/May/22 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

Thank you,
The Magnolia Team

Generated at Mon Feb 12 04:06:12 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.