Karl Guertin wrote: > On 12/12/06, Jonathan LaCour <[EMAIL PROTECTED]> wrote: >> You could even have it generate a cached version that >> gets run through a JavaScript packing tool. > > The problem with this is that unless the extraction is done on a > site-wide basis, you'll have to re-download the same set of core > components repeatedly. e.g. If one component uses only MochiKit.Async > and one uses MochiKit.Visual, you'll have to download Base and Iter > (off the top of my head) twice. It doesn't take too long before it's > quicker just to grab everything once. > > I'm interested in dojo's experimental javascript linker. It should be > possible to get it worked into the toolchain as part of the > deployment process and have it produced a minimized single download of > all the javascript in a project. AOL donated it right before 0.4, but > I haven't heard much about it since.
That sounds like a much better idea, though it requires whole-project analysis of how what libraries you use (potentially even whole-site). Then ideally you'd gzip that ahead of time, and send that gzip encoded. (By not gzipping in a filter it's a lot easier to figure out things like Content-Length.) -- Ian Bicking | [EMAIL PROTECTED] | http://blog.ianbicking.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
