Pearware Blog : Improving Java web site performance with asset caching /2008/05/01/improving-java-web-site-performance-with-asset-caching?format=rss en-us 40 agile web development Comment on Improving Java web site performance with asset caching by James <p>Very interesting article. This would be great to have on JavaLobby. If you&#8217;re interested, send me a mail and we can organise it. </p> <p>Thanks James</p> Fri, 02 May 2008 03:27:39 -0500 urn:uuid:29470be6-22a7-4a12-82fa-30db20bd24c8 http://blog.pearware.org/2008/05/01/improving-java-web-site-performance-with-asset-caching#comment-3 Comment on Improving Java web site performance with asset caching by arfio <p>pretty retarded</p> Sat, 03 May 2008 19:53:13 -0500 urn:uuid:1b89c30a-3abd-4bb3-a7b6-b2d63a47a7f1 http://blog.pearware.org/2008/05/01/improving-java-web-site-performance-with-asset-caching#comment-4 Comment on Improving Java web site performance with asset caching by Brian <p>Isn&#8217;t 1 year or 10 years overkill? Most browsers will download it again the next day because the disk caches are set (by default) to relatively small sizes. Also, if your server shows the last modification time on these static files, a lot of browsers (especially FF) have algorithms to guess at how long they should be cached.</p> Sat, 03 May 2008 21:44:23 -0500 urn:uuid:96013bc3-aba4-4acd-a92e-cf0f1cfd07b1 http://blog.pearware.org/2008/05/01/improving-java-web-site-performance-with-asset-caching#comment-7 Comment on Improving Java web site performance with asset caching by Jos Hirth <p>Yes, 10 years is overkill. For the most part 1 week will have the same effect. However, it doesn&#8217;t hurt if you&#8217;re going a bit overboard there.</p> <p>Basically the only practical reason to use really far away expired headers is marking them as will-never-change for maintainers. Once they see the header they will understand what you did there. Whereas less excessive expiring dates can be less unambiguous.</p> Sun, 04 May 2008 04:28:25 -0500 urn:uuid:5a724a09-56ff-4d01-ab76-fd0e494a4f3e http://blog.pearware.org/2008/05/01/improving-java-web-site-performance-with-asset-caching#comment-8 Comment on Improving Java web site performance with asset caching by SCdF <p>Shouldn&#8217;t your web server deal with that stuff for you?</p> Mon, 05 May 2008 01:52:29 -0500 urn:uuid:84d6d3e8-2547-4534-b80d-40d6c4314b4d http://blog.pearware.org/2008/05/01/improving-java-web-site-performance-with-asset-caching#comment-9 Comment on Improving Java web site performance with asset caching by Dmitry <p>there are several cache-related filters in JSOS: <a href="http://www.servletsuite.com/filters.htm" rel="nofollow">http://www.servletsuite.com/filters.htm</a></p> Mon, 05 May 2008 05:54:42 -0500 urn:uuid:ffcaf490-dc32-484f-a164-64c8901d2297 http://blog.pearware.org/2008/05/01/improving-java-web-site-performance-with-asset-caching#comment-11 Comment on Improving Java web site performance with asset caching by Tiago Albineli Motta <p>I think it&#8217;s better to put an apache between the client and the container.</p> Mon, 02 Jun 2008 10:01:31 -0500 urn:uuid:f22b36b6-acd4-48c6-90b0-fcaad238c2f7 http://blog.pearware.org/2008/05/01/improving-java-web-site-performance-with-asset-caching#comment-30 Comment on Improving Java web site performance with asset caching by Willie Wheeler <p>Funny, I wrote almost exactly the same filter about a week ago, for exactly the same reason (bad YSlow grade)&#8230; :-)</p> Tue, 05 Aug 2008 21:16:50 -0500 urn:uuid:cffc6341-0863-4c45-b230-5306df261f7c http://blog.pearware.org/2008/05/01/improving-java-web-site-performance-with-asset-caching#comment-224 Comment on Improving Java web site performance with asset caching by mmo <p>Great usage of asset caching. Helps a lot to read posts that explain things thoroughly.</p> Thu, 18 Sep 2008 22:55:40 -0500 urn:uuid:a182f76b-f100-4438-9975-4d7cfab423f4 http://blog.pearware.org/2008/05/01/improving-java-web-site-performance-with-asset-caching#comment-631