[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: lzlib usage
- From: Matthew Wild <mwild1@...>
- Date: Fri, 29 Jan 2010 18:10:34 +0000
On 29 January 2010 14:04, Jerome Vuarand <jerome.vuarand@gmail.com> wrote:
> 2010/1/29 Brian Maher <maherb@brimworks.com>:
>> FYI, if you want a streaming interface to zlib, you can try this out:
>>
>> http://github.com/brimworks/lua-zlib
>>
>> It is a small bit of code that I wrote for fun. Note that it
>> currently hard-codes deflateInit() and inflateInit(), but after more
>> experience of using zlib, I now know that if you want gzip headers to
>> be properly read, you need to use inflateInit2() and pass in MAX_WBITS
>> + 32 magic number for the window size :-(. I'll see about fixing
>> this.
>>
>> I should also add options so that deflateInit2() parameters may be
>> specified (give the library more flexibility).
>
> For what it's worth I also have a zlib binding available there:
>
> http://piratery.net/hg/luazlib/
>
Gah my head! :)
Prosody is currently using http://github.com/brimworks/lua-zlib - it's
working great. However other projects are using others, and LuaRocks
perhaps contains one of them (I don't know which). They all have the
same name (especially if you discount punctuation), they all have
differing APIs...
...and we need to package one of them for Debian. I haven't decided on
a solution yet, but ultimately it's hurting everyone to have multiple
incompatible libraries like this.
Matthew
- References:
- lzlib usage, Phoenix Sol
- Re: lzlib usage, Petite Abeille
- Re: lzlib usage, Phoenix Sol
- Re: lzlib usage, Ignacio Burgueño
- Re: lzlib usage, Sam Roberts
- Re: lzlib usage, Phoenix Sol
- Re: lzlib usage, GrayFace
- Re: lzlib usage, Phoenix Sol
- Re: lzlib usage, Brian Maher
- Re: lzlib usage, Jerome Vuarand