Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-64349

Add mechanism to ship Moodle with a pre-configured known browser local cache

    XMLWordPrintable

    Details

    • Affected Branches:
      MOODLE_36_STABLE, MOODLE_37_STABLE

      Description

      It would be good to ship a configuration with Moodle for a set of assets that were added during this release that are known to be required by the client browser for the user.

      We could build this asset configuration for each release and then modify Moodle so that the assets are shipped to the user's browser on their first page request and loaded into local cache ready to go.

      This helps to mitigate some of the problems we see on MoodleCloud when we add new features during a release that are heavily reliant on loading assets (e.g. templates) using AJAX and the user's first page hit for those new features triggers a large volume of network requests to fetch the assets, for example what happened when we added the new blocks in 3.6 and the first time the user visits the dashboard the browser sends 30 - 50 network requests to load the static assets.

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            ryanwyllie Ryan Wyllie
            Participants:
            Component watchers:
            Andrew Nicols, Jun Pataleta, Michael Hawkins, Shamim Rezaie, Simey Lameze, Matteo Scaramuccia, Andrew Nicols, Jun Pataleta, Michael Hawkins, Shamim Rezaie, Simey Lameze
            Votes:
            3 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 2 minutes
                2m