Tapestry
  1. Tapestry
  2. TAPESTRY-2159

YSlow Recommendation: Version bundled javascript and use far-future expires header

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.0.10
    • Fix Version/s: 5.0.12
    • Component/s: None
    • Labels:
      None
    • Environment:
      Any

      Description

      Jesse Kuhnert has already implemented this in T4. (Jira issue TAPESTRY-2122.)

      Prevents client side errors that occur if user doesn't flush browser's cache between Tapestry upgrades. (And javascript has changed.)

      See: http://developer.yahoo.com/performance/rules.html#expires

      This really applies to classpath resources. Context resources can also be versioned and (via some kind of servlet container ju-ju) hack the expires header ... but that's an application development and deployment issue seperate from Tapestry.

      Part of this requires that the Tapestry release number be available and incorporated into the mapped path for the classpath asset. See TAPESTRY-2231.

        Activity

        Mark Thomas made changes -
        Workflow Default workflow, editable Closed status [ 12568401 ] jira [ 12591457 ]
        Mark Thomas made changes -
        Workflow jira [ 12423536 ] Default workflow, editable Closed status [ 12568401 ]
        Howard M. Lewis Ship made changes -
        Fix Version/s 5.0.12 [ 12313048 ]
        Resolution Fixed [ 1 ]
        Assignee Howard M. Lewis Ship [ hlship ]
        Fix Version/s 5.1 [ 12312964 ]
        Status Open [ 1 ] Closed [ 6 ]
        Howard M. Lewis Ship made changes -
        Description Jesse Kuhnert has already implemented this in T4. (Jira issue TAPESTRY-2122.)

        Prevents client side errors that occur if user doesn't flush browser's cache between Tapestry upgrades. (And javascript has changed.)
        Jesse Kuhnert has already implemented this in T4. (Jira issue TAPESTRY-2122.)

        Prevents client side errors that occur if user doesn't flush browser's cache between Tapestry upgrades. (And javascript has changed.)

        See: http://developer.yahoo.com/performance/rules.html#expires

        This really applies to classpath resources. Context resources can also be versioned and (via some kind of servlet container ju-ju) hack the expires header ... but that's an application development and deployment issue seperate from Tapestry.

        Part of this requires that the Tapestry release number be available and incorporated into the mapped path for the classpath asset. See TAPESTRY-2231.
        Summary Version bundled javascript YSlow Recommendation: Version bundled javascript and use far-future expires header
        Howard M. Lewis Ship made changes -
        Field Original Value New Value
        Fix Version/s 5.0.11 [ 12312968 ]
        Fix Version/s 5.1 [ 12312964 ]
        Ville Virtanen created issue -

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Ville Virtanen
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development