A solution for the *.cache.html files is to gzip them
to .cache.html.gz files.
If you are using Apache as your web server you can then modify the
mime.conf file (found at /etc/apache2/mods-enabled/mime.conf) by
uncommenting:
AddEncoding x-gzip .gz .tgz
and commenting:
#AddType application/x-gzip .gz .tgz
This means that my apache server will send the .cache.html.gz files in
replacement for the .cache.html files and also send the response
header: content-encoding=gzip
This can also be done in a .htaccess file (RemoveType and AddEncoding)
placed in the cache folder.
On Jul 22, 7:06 am, martinhansen <[email protected]>
wrote:
> Hello,
>
> I am evaluating some approaches to reduce the amount of data being
> transmitted to the client browser. I am using the Apache Tomcat web
> server. I successfully managed to enable GZIP output for the Tomcat
> server by editing the server config file. It works fine. However, this
> way the data is compressed on-the-fly by the web server for every
> request which considerably increases server CPU load. Is this
> assumption correct?
>
> Is there a way to pre-compress the contents of my GWT app and have
> this pre-compressed content delivered by the web server?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" 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/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---
