This content has been marked as final.
Show 2 replies
-
1. Re: How does the 304 Modification Checks work in 7.x?
bonigv Oct 10, 2013 6:48 AM (in response to bonigv)My war is around 2GB in size. It is that big because of the way GWT compiles for multiple languages and browsers. The static content is burhied deep within the war. It seems that ETag based evaluation of 304 check degrades considerably with te size of WAR. Does Jboss keep a tree in memory or does it use the disk checksum to decide on Etag modifications? Seems like server is doing something very time consuming to evaluate content expiry check. And it seems the algorithm is not optimized for large WARs
-
2. Re: How does the 304 Modification Checks work in 7.x?
heiko.braun Oct 10, 2013 6:55 AM (in response to bonigv)GWT apps tend to be big after compilation, but 2GB is way too big. Try tweaking the GWT compiler settings to create obfuscated javascript code. See http://www.gwtproject.org/doc/latest/FAQ_DebuggingAndCompiling.html for further details