Lines Matching refs:deflate

33  5. deflate() or inflate() returns Z_BUF_ERROR.
38     Z_BUF_ERROR is not fatal--another call to deflate() or inflate() can be
130 18. Why does gzip give an error on a file I make with compress/deflate?
132     The compress and deflate functions produce data in the zlib format, which
148     You can request that deflate write the gzip format instead of the zlib
181     update the version strings in deflate.c and inftrees.c.
218     deflate stream once to generate an index, and then use that index for
229     understand the deflate format?
243     Yes.  inflate() and deflate() will process any amount of data correctly.
244     Each call of inflate() or deflate() is limited to input and output chunks
249     inflate() or deflate().  The application can easily set up its own counters
250     updated after each call of inflate() or deflate() to count beyond 4 GB.
297 36. Valgrind (or some similar memory access checker) says that deflate is
301     No.  That is intentional for performance reasons, and the output of deflate
322 39. What's the difference between the "gzip" and "deflate" HTTP 1.1 encodings?
324     "gzip" is the gzip format, and "deflate" is the zlib format.  They should
326     the raw deflate compressed data format.  While the HTTP 1.1 RFC 2616
327     correctly points to the zlib specification in RFC 1950 for the "deflate"
329     incorrectly produce or expect raw deflate data per the deflate
331     "deflate" transfer encoding using the zlib format would be the more