I'm not sure this always makes sense to do. One of our applications has a couple wizard-like interfaces where you answer a few items and move through until the end. Each page had a tiny little bit of page-specific JavaScript to be delivered in addition to the common JavaScript (Prototype, Tapestry, etc). If Tapestry is always re-packaging all of the JavaScript, plus the small page-specific JavaScript, into a single JavaScript file, isn't this more wasteful? The browser can't cache Prototype, but has to re-download it each time, right?
Thanks, mrg On Fri, Oct 15, 2010 at 12:19 PM, Howard Lewis Ship <hls...@gmail.com> wrote: > That article doesn't take into account the things that Tapestry does for you: > - Combines prototype.js with other JS files to form a single JS file > (this is done on-the-fly) > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
