Author: buildbot
Date: Tue Feb 5 12:20:50 2013
New Revision: 849475
Log:
Production update by buildbot for tapestry
Modified:
websites/production/tapestry/content/cache/main.pageCache
websites/production/tapestry/content/component-libraries.html
Modified: websites/production/tapestry/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/tapestry/content/component-libraries.html
==============================================================================
--- websites/production/tapestry/content/component-libraries.html (original)
+++ websites/production/tapestry/content/component-libraries.html Tue Feb 5
12:20:50 2013
@@ -293,7 +293,7 @@ table.ScrollbarTable td.ScrollbarNextIco
<p>Classpath assets, those packaged in JAR files (such as the happy.jpg asset)
are retrieved by the client web browser using a URL that reflects the package
name. Tapestry users a special virtual folder, /assets, under the context
folder for this purpose.</p>
-<p>The image file here would exposed to the web browser via the URL
/happyapp/assets/org/example/happylib/components/happy.jpg (this assumes that
the application was deployed as happyapp.war).</p>
+<p>The image file here is exposed to the web browser via the URL
/happyapp/assets/org/example/happylib/components/happy.jpg (this assumes that
the application was deployed as happyapp.war).</p>
<p>Tapestry uses a far-future expiration date for classpath assets; this
allows browsers to aggressively cache the file, but in Tapestry 5.1 and earlier
this causes a problem when a later version of the library changes the file.
This is discussed in detail in <a shape="rect" class="external-link"
href="http://developer.yahoo.com/performance/rules.html#expires"; >Yahoo's
Performance Best Practices</a>.</p>
