hi ntdeaf! i know how to setup apache, mod_jk and tomcat. my question was more in the direction of using mod_deflate on apache or using the compression capabilities of tomcat. and for which files? i mean as far as i know ie6 pre sp2 has a bug so it cannot handle compressed js files, and this is why the generated files are called cache.html and not cache.js, except the loaded (nocache.js) so i suppose it is save to compress everything except the nocache.js. so that is about compression, now what's about cache headers. Etag and co? here i think that since the generated files names come from MD5, it is also save to tell the browser to cache the files for ever and never come back to check them... any practical experience on production with these topics? anything else i should take care of when going to production?
thanks Michael On Feb 26, 5:12 pm, ntdeaf <[email protected]> wrote: > Hi, > > I'm using a setup just as you have described, and have found no > difference with running the webapp native on a tomcat (without apache > http). It just takes a little more configuration to make the webapp > known to apache, but that is normal since I'm using mod_jk. > > If you need any more info on how to set this up, let me know.. > > NTDeaf > > On Feb 25, 8:07 pm, mmoossen <[email protected]> wrote: > > > dear all! > > > i just wanted to know what are the best practices for serving my gwt > > app in production. > > i mean, in my case, there will be an apache http server in front of > > tomcat communicating via mod-jk. > > so, what are your experiences with compression, setting cache headers, > > etc? > > > thanks > > Michael -- 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.
