Coda: The application version IS still used in exception reports (both the
HTML version and, if memory servers, the new text file written to the file
system).
On Thu, Oct 23, 2014 at 3:33 PM, Paul Stanton wrote:
> great!
>
>
> On 24/10/2014 8:37 AM, Howard Lewis Ship wrote:
>
>> That is correct;
great!
On 24/10/2014 8:37 AM, Howard Lewis Ship wrote:
That is correct; tapestry.application-version is no longer needed. Each
individual asset gets its own content fingerprint. This has huge
implications for upgrades of you application, as often, all the unchanged
assets will maintain the same
That is correct; tapestry.application-version is no longer needed. Each
individual asset gets its own content fingerprint. This has huge
implications for upgrades of you application, as often, all the unchanged
assets will maintain the same fingerprint, and already be present in the
end-user's bro
https://github.com/apache/tapestry-5/blob/master/54_RELEASE_NOTES.md#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
