Thanks.
On Sep 7, 8:18 pm, Thomas Arp <[email protected]> wrote:
> Basically you have a few options.
>
> -- Since the generated file is "static" content, you can distribute it
> to a content delivery network.
> -- Make sure to have enabled gzip compression on the web server. It
> makes a lot of difference.
> -- Make sure you let the client cache the cachable files. Never let
> the cache expire.
> -- Make sure you compile to OBF - the files are notably smaller
> (30-40%).
> -- If you have some parts of your program that is likely to change
> relatively often, put it into its own module.
>
> An uncompressed PRETTY file will be about 8-12 times bigger than a
> compressed OBF file.
>
> Most of these things will help. However, it is generally a good idea
> to also add a sort of "wait" image on first load. A typical GWT-Ext
> site will require download of quite a few large files, for example the
> compiled file (.cache.html) and the necessary library files (ext.js
> and friends). Even on a fast line, downloading a couple of megabytes
> will take a while.
>
> /Thomas Arp
>
> On Sep 7, 10:20 am, mmannarino <[email protected]> wrote:
>
>
>
> > Hi guys,
> > Someone knows how to optimize generated html.cache file?
> > What's the better way to optimize a gwt application and generated
> > html .cache?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"GWT-Ext Developer Forum" 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/gwt-ext?hl=en
-~----------~----~----~----~------~----~------~--~---
