Hi all! I've just read this articles: http://developer.yahoo.com/performance/rules.html http://yuiblog.com/blog/2007/04/11/performance-research-part-4/
It might be interresting to make some changes to Wicket to better handle some rules.. For example, I was thinking of: * "Add an Expires Header" - http://developer.yahoo.com/performance/rules.html#expires Wicket already set a short term expiration for bundled JS, CSS, images resources. We could get better caching performance by using ressources names with versions and than using long term caching.. The drawback is an updated resource must have its name changes.. At least it would be nice to overide this expiration * "Move Scripts to the Bottom" - http://developer.yahoo.com/performance/rules.html#js_bottom Handling this in IHeaderResponse implementation? * "Configure ETags" - http://developer.yahoo.com/performance/rules.html#etags Plugging this with page cache? * "Maximizing Parallel Downloads" By using some automatic round-robin absolutes URL for resources downloading.. It would means more configuration for setting absolute URL pool for each resources types (CSS, images, JavaScript..) Stéphane -- View this message in context: http://www.nabble.com/Hints-for-improved-web-performances-tf4206588.html#a11965982 Sent from the Wicket - Dev mailing list archive at Nabble.com.
