[Bug 2048] HTTP transport should be compressed

[bugzilla-daemon at icedtea.classpath.org]

http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=2048

--- Comment #2 from Severin Gehwolf <sgehwolf at redhat.com> ---
The idea was to compress client *and* server side. That is agent (as one
client) would compress, server (web-endpoint) would deflate and process. If
there is a response compress that too and agent would deflate. Same for cli and
gui clients. Why are you asking? Sure, it would mean more CPU cycles are spent
for compression/deflation but this shouldn't be significant. If you are worried
about extra overhead we could surely make this configurable. Though, it would
be trading extra CPU cycles for less time being spent on sending traffic over
the wire.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/distro-pkg-dev/attachments/20141027/31900fd5/attachment.html>