Lines Matching refs:deflate

32  5. deflate() or inflate() returns Z_BUF_ERROR.
37     Z_BUF_ERROR is not fatal--another call to deflate() or inflate() can be
129 18. Why does gzip give an error on a file I make with compress/deflate?
131     The compress and deflate functions produce data in the zlib format, which
147     You can request that deflate write the gzip format instead of the zlib
180     update the version strings in deflate.c and inftrees.c.
217     deflate stream once to generate an index, and then use that index for
228     understand the deflate format?
242     Yes.  inflate() and deflate() will process any amount of data correctly.
243     Each call of inflate() or deflate() is limited to input and output chunks
248     inflate() or deflate().  The application can easily set up its own counters
249     updated after each call of inflate() or deflate() to count beyond 4 GB.
296 36. Valgrind (or some similar memory access checker) says that deflate is
300     No.  That is intentional for performance reasons, and the output of deflate
321 39. What's the difference between the "gzip" and "deflate" HTTP 1.1 encodings?
323     "gzip" is the gzip format, and "deflate" is the zlib format.  They should
325     the raw deflate compressed data format.  While the HTTP 1.1 RFC 2616
326     correctly points to the zlib specification in RFC 1950 for the "deflate"
328     incorrectly produce or expect raw deflate data per the deflate
330     "deflate" transfer encoding using the zlib format would be the more