This content has been marked as final.
Show 5 replies
-
1. Re: Seam 2.0.0.GA, compression beyond tomcat-connector compr
dhartford Nov 30, 2007 8:17 AM (in response to dhartford)Does Seam 2.0.0.GA have some type of compression filter that can be configured, or is there something other than the Tomcat Connector (jboss 4.2.1) that is causing the over-the-wire gzip compression to the browser?
-D -
2. Re: Seam 2.0.0.GA, compression beyond tomcat-connector compr
pmuir Nov 30, 2007 8:48 AM (in response to dhartford)Nothing in Seam.
-
3. Re: Seam 2.0.0.GA, compression beyond tomcat-connector compr
dhartford Dec 5, 2007 11:08 AM (in response to dhartford)The compression IS happening in Seam.
In the GWTService class, the method:protected boolean shouldCompressResponse(HttpServletRequest request, HttpServletResponse response, String responsePayload)
* This implementation currently returns <code>true</code> if the response
* string's estimated byte length is longer than 256 bytes.
This is not configurable other than subclassing GWTService.
Workaround: In I.E. at least, you can disable HTTP/1.1 and only use HTTP/1.0 so you can see the packets without being compressed. -
4. Re: Seam 2.0.0.GA, compression beyond tomcat-connector compr
dhartford Dec 5, 2007 11:29 AM (in response to dhartford)opened JIRA ticket for discussion and direction:
http://jira.jboss.org/jira/browse/JBSEAM-2350 -
5. Re: Seam 2.0.0.GA, compression beyond tomcat-connector compr
pmuir Dec 5, 2007 12:28 PM (in response to dhartford)Ah, sorry, my bad, I don't know anything about remoting and didn't read your post properly :(