nice we are also taking efforts in optimizing the webapp
as we serve the resources (images/css/js) using 3rd content provider, our approach is different from your wicket-focus turning; but it indeeds give me some insight, thanks we also want to "merge" the css/js files, but after thinking carefully, it can't work for us because we are using "header contribution" at different panels, it is very flexible for the designers to split the css/js files according to the panel and they like it very much for the flexibility, maintainability and reusability however, since a panel can hide/show dynamically for the same url in different times (though not common, but we can't avoid that), that means we can't simply "merge" different css/js files from different panels for the given page Stefan Fußenegger wrote: > > I just finished the 4th and last entry of my series "Wicket Interface > Speed-Up" on my blog. To give a short summary: I investigated one of my > apps with YSlow and started optimizing it's interface rendering speed [1]. > Especially Wicket's way of handling resources, i.e. JS and CSS files, > causes interfaces to load rather slowly. In my articles, I explain how to > modify the cache interval [2], how to mount resources with a version (e.g. > /css/all-1234.css) in order to use aggressive client-side caching (e.g. > resources expire after a year) [3]. Finally, I show how to merge resources > at application startup (using a class classed MergedResourceStream) to > reduce the number of resources a client has to download [4], including > code). I was able to increase interface loading times considerably, so > it's surely worth a look. > > I feel that it would also be worth to discuss, whether this work could be > part of upcoming Wicket versions. For the time being I'd like to make the > code attached to [4] a wicketstuff project - sfussenegger needs commit > access ;) - and wait for your feedback. > > The links: > [1] > http://talk-on-tech.blogspot.com/2008/08/wicket-interface-speed-up.html > Wicket Interface Speed-Up > [2] > http://talk-on-tech.blogspot.com/2008/08/wicket-interface-speed-up-modifying.html > Wicket Interface Speed-Up: Modifying Expires and Cache-Control Headers > [3] > http://talk-on-tech.blogspot.com/2008/08/wicket-interface-speed-up-caching.html > Wicket Interface Speed-Up: Caching Resources Forever > [4] > http://talk-on-tech.blogspot.com/2008/08/wicket-interface-speed-up-merging.html > Wicket Interface Speed-Up: Merging Resources for Fewer HTTP Requests > -- View this message in context: http://www.nabble.com/Discussion-on-%22Wicket-Interface-Speed-Up%22-tp19197540p19212465.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
