On Tue, 28 Apr 1998, Werner Koch wrote:
Lindsay Mathieson <lindsay(_at_)powerup(_dot_)com(_dot_)au> writes:
Why not just document the usage of zlib - A new compression algorithm would
break existing implementations and compatibility is one of the objectives
for the spec.
PGP used an early version of zlib which was limited to a 13 bit
compression window, the RFC documented zlib does not have this
limitation. It's okay to support the old version, but why should
I not use a newer (and documented) one as an option?
The other zlibism is that I still need to pass the value -15 in
inflateInit2 instead of using InflateInit since the latter will place a
gzip(?) style header in front and crc at the end. This is undocumented
(except maybe in inflate.c)
It would be reasonable to use a new algorithm ID to add a direct zlib
feature.
--- reply to tzeruch - at - ceddec - dot - com ---