I wrote Archive::Zip, so I have a fair amount of experience with Compress::Zlib (though much of it is second-hand). I know of no one who has had problems with it after about version 1.06. Prior to that version, it would damage data sometimes when compressing.
Overall, I'd say it's quite stable. It's being used in the guts of ActiveState's PPM, for instance. Archive::Tar uses it for its file (de)compression, and Archive::Zip uses it for its member (de)compression. There are other interfaces to it, including IO::Zlib that lets you view a gzip stream as a file handle. This may be easier to use, depending on your application. | [reply] |
I have used Compress::Zlib a few times in the past on both unix (Linux,SunOS,HP and IRIX) as well as Win32 with very few failures. I find it to be stable, but (always a catch) i write production unix code, but not Win32 code, so i am unfortunatly not too much help on the long term stability on Windows ... but, assuming the code is reasonably similar, i would expect it to be stable.
All that, and i managed not to help ... sorry
OH, a sarcasm detector, that’s really useful | [reply] |
I use Compress::Zlib on production code.
It's on Linux, so I can't guarantee that translates 100% to windows, although I'd hazard a guess that it's as stable.
The scripts I've got going run through about 40GB of data per week, and integrity checks show it's having no problems at all..
I'd say it's plenty stable enough (currently it's on a run of about 140GB, and it's quite merry).
Cheers,
Malk | [reply] |
