tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From hls...@apache.org
Subject [14/14] git commit: Add release notes about content hash in the URL
Date Thu, 14 Mar 2013 23:09:18 GMT
Updated Branches:
  refs/heads/master 8a29dbfbd -> 53c3611ed

Add release notes about content hash in the URL

Project: http://git-wip-us.apache.org/repos/asf/tapestry-5/repo
Commit: http://git-wip-us.apache.org/repos/asf/tapestry-5/commit/53c3611e
Tree: http://git-wip-us.apache.org/repos/asf/tapestry-5/tree/53c3611e
Diff: http://git-wip-us.apache.org/repos/asf/tapestry-5/diff/53c3611e

Branch: refs/heads/master
Commit: 53c3611ed7a14cb106173b2172a82574c870cf05
Parents: fd09dff
Author: Howard M. Lewis Ship <hlship@apache.org>
Authored: Thu Mar 14 16:08:25 2013 -0700
Committer: Howard M. Lewis Ship <hlship@apache.org>
Committed: Thu Mar 14 16:08:25 2013 -0700

 54_RELEASE_NOTES.txt |   14 ++++++++++++++
 1 files changed, 14 insertions(+), 0 deletions(-)

diff --git a/54_RELEASE_NOTES.txt b/54_RELEASE_NOTES.txt
index 8c369c6..75f9ac2 100644
--- a/54_RELEASE_NOTES.txt
+++ b/54_RELEASE_NOTES.txt
@@ -34,6 +34,20 @@ to running initialization functions, deals with DOM updates better, and
is overa
 Tapestry is moving away from "magic class names" to a more uniform approach based on the
use of HTML 5 compliant `data-`
+## Asset Improvements
+Prior versions of Tapestry created cacheable URLs for Assets that incorporated the application
version number. The
+Assets were served with a far-future expires header: the client browser would not even need
to check to see
+if the asset had changed.
+Unfortunately, when any asset changed in a new deployment of the application, the version
number needed to
+change, resulting in all assets being downloaded (because the application version number
in their URLs changed).
+In this release, individual assets are given a checksum based on the asset's content. When
the underlying
+file is changed, the asset will be served with the new URL, but unchanged assets will not
be affected. This means
+that when redeploying your application, you'll see far less asset traffic, as most client
web browsers will already
+have most assets (whose contents have not changed) in their local cache.
 ## ControlGroup Mixin
 This new mixin for Field components adds the outer <div> and <label> elements
for a Field to layout correctly

View raw message