Hello Vladan,
1- Zlib deflate/inflate does not store the file information... it is
used only to compress a stream of data. The gzip file format uses the
zlib deflate/inflate and adds a header to store the file info.
2- No... that's why in the unix world people typically use tar + gzip.
But of course you can simply build your own file format.
3- Yes the armlet port also has the 68k code and works on older devices.
Good luck.
Jerome
Vladan Markovic wrote:
Hi,
I am working with ZLib library, and there is couple of things that it`s
not very clear to me, i will appreciate if some one can help me. I am using
ZLib ARMlet found on http://www.copera.com/zlib-armlet/ , it`s working ok on
internal databases.
1. I manage to compress file on external storage using VFS functions, i
noticed that compresed data is exactly the same as data created with other
compresion program like LightNZip , RescoExplorer ... but with one diference
those programs create ( 30 bytes + 'name of file') in the beginig of file
like some kind of header. Is this some standard header for compressed files
i dint find anything in the manual, or is this some kind of agreament
beatween companies to archive compatibility ???
2. Does zlib have native support for compressing more than one file to
one archive, or this must be implemented by developer, is there some
standard to, i also notice compatibility between programs i mentioned before
when archive is compressed on memory card.
3. Does ARMlet port of zlib SysZlib.prc can work properly on Motorola
68k devices, or i need to install different zlib prc lib.
Thank you,
Vladan Markovic
www.cyberart.co.yu
--
For information on using the PalmSource Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
