Hi, I think it's fine to have this parameter configurable. One
question here though - does one have to provide the same
windowsBits value to inflateInit2 func call on decompression as it
was during compression? If that's true - you should persist the
value along with the compressed block and reuse it during
decompression. Which is probably fine too but needs a bit more
work.
Thanks, Igor
On 12/18/2019 11:45 AM, Xiyuan Wang
wrote:
|
_______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx