I know this is an old thread, but I've been working on a T4.1.1 application for a long time and it's about to go live. Our recent live site testing shows that these huge .js files kill the initial page load and they aren't really getting cached by the browser, so they transfer on *every* page load.
I'm curious to know... 1. What happened to the stripped and compressed dojo file here Jessek mentioned? 2. If it's not around / in use, what dojo packages does T4.1.1 need and how do I do a custom build (a good url would b fine). 3. Why aren't these resources getting cached? I've modified the T4.1.1 asset service to deliver just an "Expires" and "Cache-control" header, but the browser still fetches them every time. I played with T5 a few months ago, but haven't been following it for a while. Has this been solved in T5? Many thanks everyone! > Just as an update on this thread, it looks like they've been working on > build size and I'm currently able to create a 23kb file for dojo..So, I > hope > that will speed things up a little bit. -- View this message in context: http://www.nabble.com/Tapestry-4.1%3A-dojo-everywhere--tp5650151p18455280.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
