Uploaded image for project: 'Seam 2'
  1. Seam 2
  2. JBSEAM-2723

Page fragment caching for plugin render

    Details

    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2.1.0.GA
    • Component/s: Wiki
    • Labels:
      None

      Description

      The infrastructure for page fragment caching with EHCache is in place. We need to cache plugin-rendered HTML fragments with this strategy:

      • generate a unique cache key for each plugin, including the document ID and the macro hashcode (including position and parameters)
      • use a separate region for each plugin type, so that we can invalidate the cache for the whole region ("remove all cached fragments of a certain plugin no matter on what document it is rendered")
      • build cache regions on startup based on plugin metadata

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  christian.bauer Christian Bauer
                  Reporter:
                  christian.bauer Christian Bauer
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: