On Mon, Mar 28, 2022 at 7:33 PM Alan Bateman wrote:
>
> On 28/03/2022 11:02, Volker Simonis wrote:
> > :
> > As I wrote before, the extra data written into the output buffer isn't
> > sensitive because it can only originate from the history buffer (aka
> > "sliding window"). Also, this data is
On 28/03/2022 11:02, Volker Simonis wrote:
:
As I wrote before, the extra data written into the output buffer isn't
sensitive because it can only originate from the history buffer (aka
"sliding window"). Also, this data is already exposed today if the
`Inflater` class is being used stand-alone,
On Mon, Mar 28, 2022 at 10:53 AM Alan Bateman wrote:
>
> On 22/03/2022 12:28, Volker Simonis wrote:
> > :
> > I don't really understand this concern? Do you mean what happens if
> > another thread is changing the content of the output buffer during an
> > inflate? I think such a use case has
On 22/03/2022 12:28, Volker Simonis wrote:
:
I don't really understand this concern? Do you mean what happens if
another thread is changing the content of the output buffer during an
inflate? I think such a use case has never been well-defined and
amending the specification won't change anything
On Mar 22, 2022, at 12:28 PM, Volker Simonis
mailto:volker.simo...@gmail.com>> wrote:
On Mon, Mar 21, 2022 at 8:24 PM Lance Andersen
mailto:lance.ander...@oracle.com>> wrote:
Hi Lance,
Thanks for looking into this issue. Please find my answers inline:
Hi Volker,
I have read through what
On Mon, Mar 21, 2022 at 8:24 PM Lance Andersen
wrote:
Hi Lance,
Thanks for looking into this issue. Please find my answers inline:
> Hi Volker,
>
> I have read through what you have provided/pointed to, thank you, and on the
> surface what you are suggesting sounds reasonable.
>
> That being
On Mon, Mar 21, 2022 at 8:19 PM Alan Bateman wrote:
>
Hi Alan,
Thanks for looking at this issue. Please find my answers to your
questions inline:
> On 04/03/2022 10:04, Volker Simonis wrote:
> > :
> >
> > 1. Relax the specification of `InflaterInputStream::read(..)` and
> > specifically note
Hi Volker,
I have read through what you have provided/pointed to, thank you, and on the
surface what you are suggesting sounds reasonable.
That being said given that this API dates back to 1997ish, I think we have to
be careful not introduce any regressions with existing applications with the
On 04/03/2022 10:04, Volker Simonis wrote:
:
1. Relax the specification of `InflaterInputStream::read(..)` and
specifically note in the API documentation that a call to
`InflaterInputStream::read(byte[] b, int off, int len)` may write more
than *k* characters into `b` where *k* is the returned
Ping...
On Thu, Mar 10, 2022 at 8:26 PM Lance Andersen
wrote:
> Hi Volker,
>
> Thank you for the reminder
>
> This is on my radar as well but have not had a chance spend any time on
> this as yet.
>
>
>
> On Mar 9, 2022, at 2:33 PM, Volker Simonis
> wrote:
>
> @Alan, @Lance,
>
> Sorry for my
On 09/03/2022 19:33, Volker Simonis wrote:
@Alan, @Lance,
Sorry for my obtrusiveness, but what's your opinion on this issue?
I saw your mail but I haven't had time to study it yet and see if the
spec option you prefer is the best. I will try to get time next week.
-Alan
@Alan, @Lance,
Sorry for my obtrusiveness, but what's your opinion on this issue?
Thank you and best regards,
Volker
On Fri, Mar 4, 2022 at 11:04 AM Volker Simonis wrote:
>
> `java.util.zip.Inflater` is the Java wrapper class for zlib's inflater
> functionality. `Inflater::inflate(byte[]
`java.util.zip.Inflater` is the Java wrapper class for zlib's inflater
functionality. `Inflater::inflate(byte[] output, int off, int len)`
currently calls zlib's native `inflate(..)` function and passes the
address of `output[off]` and `len` to it via JNI.
The specification of zlib's
13 matches
Mail list logo
