Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-5828

Add ability to deal with javascript and css caching by client applications

    Details

    • Type: New Feature New Feature
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Analysis, Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-1017Ability to centralize application specific JavaScript/CSS files
      KULRICE-8418Add ability to ServiceRegistry page to clear application held caches
      KULRICE-4119add the ability to include multiple css & javascript files to portal pages
      KULRICE-1164Account for new KNS documentation from enhancement proposal - https://test.kuali.org/confluence/display/KULRICE/Ability+to+customize+page.tag+imported+CSS+and+Javascript
      KULRICE-14123Add init view caching ability
      KULRICE-9915Add line client Javascript runs for over a minute
      KULRICE-3939Suggest strategy for dealing with client application overrides of Hibernate annotations
      KULRICE-6683Add a "THIN" client run mode to KEW, KIM, and KSB modules
      KULRICE-6351Add ability to disable usage of security for the ServiceRegistry on the client side
      KULRICE-4528Implement ability for rice server to know what version of a client server they are calling
    • Rice Module:
      KRAD
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      For example if we have a file like "screen.css" then a client application could potentially cache that indefinitely even if we update it on the server. I've seen this handled in frameworks like rails (or possibly scss?) by setting up urls like this:

      <link href="/stylesheets/screen.css?1319289187" media="screen, projection" rel="stylesheet" type="text/css" />
      

      By adding that numeric tag on the end, that allows for the next time the screen.css is updated that it can use a new number, forcing the client to reload the latest version of the css (same tactic could be applied to javascript).

      Another thing to look at is ETags. At any rate, I'm sure there's some open source solution in the java or javascript world to help to deal with such a thing. If not, it could be done with a custom servlet.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Eric Westfall
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Structure Helper Panel