zlib 1.2.1
Publisher's Description:
zlib - The latest version of the zlib compression library, a free data-compression library that can be used on any type of computer and OS has been released by authors Jean-Loup Gailly and Mark Adler. Integrity checks on the uncompressed data are performed using either the CRC-32 checksum, which is more reliable, or the ADLER 32 checksum, which slightly less reliable but much faster. Developers can use this library to add general-purpose file-based and in-memory compression and decompression capabilities to their applications. For in-memory operations, the zlib compressed data format (RFC 1950) is used, which is designed to be fast and compact. For its compression algorithm (the only one it supports), deflate (RFC 1951) is used, employing an LZ77 compression variant and Huffman coding. Overhead expansion is five bytes per 32 KB block, plus six bytes for the entire stream, which is very small compared to what the LZW method can do. According to the authors, LZW can double or triple file sizes in extreme cases. The authors claim that typical compression ratios of zlib are between 2:1 and 5:1. The gzip format, RFC 1952, is supported. However, it only supports compressing files on a file system: no in-memory operations. The gzip format includes the directory information of individual files. Again, the format uses the deflate compression algorithm. It lacks support for the following formats/methods: PKZip 4.5, BZip2, and Deflate64.
Latest Changes:
- Remove a tab in contrib/gzappend/gzappend.c
- Update some interfaces in contrib for new zlib functions
- Update zlib version number in some contrib entries
- Add Windows CE definition for ptrdiff_t in zutil.h [Mai, Truta]
- Support shared libraries on Hurd and KFreeBSD [Brown]
User License Agreement:
http://www.gzip.org/zlib/zlib_license.html
Social bookmarks:
RSS: 
Latest User Reviews:
htnbleonm
2006-11-11 07:12:56
Version: 1.2.1
Could zlib zipp 2-byes characters filename?
Could zlib component could zipping Chinese File names ( 2 bytes a character) ?
jrbaker
2007-05-18 12:15:25
Version: 1.2.1
Everything but output
So I downloaded the DLL, wired it into my C++ project, read the code comments about the params, malloced some buffer space, loaded the input buffer with some test data and ran. Everything looked good. Buffer pointers moved, "avail_in" decremented properly, function return made sense. But the output buffer was just garbage. I even chose compression level = 0, so the the input would just move into the output without compression. Output buffer still garbage. So I must be doing something wrong, but what ? THERE IS NO EXAMPLE OF USAGE, so I have no golden start point from which to explore my options. This is a major lack of the documentation.
Social bookmarks:
RSS:
Audio & Multimedia
Development
Active X
