Thanks Alan. I dropped the current in setLevel. Yes, I would like to
be explicit about the
deflate invocation here, as the implementation clearly just calls the
deflate() blindly with
the old level/strategy after the level/strategy changed, regardless
whether there is really
anything in the
On 15/09/2013 19:30, Xueming Shen wrote:
Thanks Alan. I dropped the current in setLevel. Yes, I would like to
be explicit about the
deflate invocation here, as the implementation clearly just calls the
deflate() blindly with
the old level/strategy after the level/strategy changed, regardless
Updated accordingly.
http://cr.openjdk.java.net/~sherman/8020687/webrev/
Thanks!
-Sherman
On 9/15/13 12:45 PM, Alan Bateman wrote:
On 15/09/2013 19:30, Xueming Shen wrote:
Thanks Alan. I dropped the current in setLevel. Yes, I would like
to be explicit about the
deflate invocation here, as
On 13/09/2013 20:44, Xueming Shen wrote:
Hi,
This is change to clarify the java doc to match the existing behavior.
If there is a pending level/strategy change (via
setLevel/Stragety()) when
deflate(...) is invoked, the implementation goes down to zlib's
deflateParams()
for deflating
Hi,
This is change to clarify the java doc to match the existing behavior.
If there is a pending level/strategy change (via setLevel/Stragety()) when
deflate(...) is invoked, the implementation goes down to zlib's
deflateParams()
for deflating operation, which clearly specifies its behavior
