• Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 2.5.0-alpha1, 2.5.0
    • None
    • frontend
    • None

      Instead of having components always ask the backend for immutable data, we should request it only once and store it in the frontend.

        This is the controller panel for Smart Panels app

            [OPT-2151] Spike: Request immutable data only once

            We only cache truly immutable data for now. Adding heuristics to cache mutable data would introduce too much complexity for too little benefit. omran.abazeed also had the idea to control caching via the cache-control response header, allowing the backend to control how the browser caches data and reducing frontend complexity. I like this idea and propose to discuss this in the next team meeting.

            Sebastian Stamm added a comment - We only cache truly immutable data for now. Adding heuristics to cache mutable data would introduce too much complexity for too little benefit. omran.abazeed also had the idea to control caching via the cache-control response header, allowing the backend to control how the browser caches data and reducing frontend complexity. I like this idea and propose to discuss this in the next team meeting.

            We agreed to do this caching via the browser mechanisms instead of using custom frontend code. I created OPT-2177 for this and reverted the changes for this ticket as they did not work in all cases.

            Sebastian Stamm added a comment - We agreed to do this caching via the browser mechanisms instead of using custom frontend code. I created OPT-2177 for this and reverted the changes for this ticket as they did not work in all cases.

              Unassigned Unassigned
              sebastian.stamm Sebastian Stamm
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: