Greg Stark <gsstark@mit.edu> wrote:
> I suspect if this was a problem the zlib people would have added
> internal buffering ages ago. I find it hard to believe we're not the
> first application to use it this way.
I think that most uses of this library are on entire files or streams.
They may have felt that adding another layer of buffering would just
hurt performance for the typical use case, and anyone using it in some
other way could always use their own buffering layer. In Java adding
that layer took 30 characters of code, so it didn't make a very big
impression on me -- it took a while to even remember I'd had to do it.
-Kevin