Rev 1896 | Go to most recent revision | Show entire file | Regard whitespace | Details | Blame | Last modification | View Log | RSS feed
Rev 1896 | Rev 3926 | ||
---|---|---|---|
Line 42... | Line 42... | ||
42 | heavily annotated example. |
42 | heavily annotated example. |
43 | 43 | ||
Line 44... | Line 44... | ||
44 | 6. Where's the zlib documentation (man pages, etc.)? |
44 | 6. Where's the zlib documentation (man pages, etc.)? |
Line 45... | Line 45... | ||
45 | 45 | ||
46 | It's in zlib.h . Examples of zlib usage are in the files example.c and |
46 | It's in zlib.h . Examples of zlib usage are in the files test/example.c |
Line 47... | Line 47... | ||
47 | minigzip.c, with more in examples/ . |
47 | and test/minigzip.c, with more in examples/ . |
Line 48... | Line 48... | ||
48 | 48 | ||
49 | 7. Why don't you use GNU autoconf or libtool or ...? |
49 | 7. Why don't you use GNU autoconf or libtool or ...? |
Line 82... | Line 82... | ||
82 | the code of uncompress on your own. |
82 | the code of uncompress on your own. |
83 | 83 | ||
Line 84... | Line 84... | ||
84 | 13. How can I make a Unix shared library? |
84 | 13. How can I make a Unix shared library? |
Line -... | Line 85... | ||
- | 85 | ||
- | 86 | By default a shared (and a static) library is built for Unix. So: |
|
85 | 87 | ||
86 | make clean |
88 | make distclean |
87 | ./configure -s |
89 | ./configure |
Line 88... | Line 90... | ||
88 | make |
90 | make |
Line 89... | Line 91... | ||
89 | 91 | ||
Line 323... | Line 325... | ||
323 | the raw deflate compressed data format. While the HTTP 1.1 RFC 2616 |
325 | the raw deflate compressed data format. While the HTTP 1.1 RFC 2616 |
324 | correctly points to the zlib specification in RFC 1950 for the "deflate" |
326 | correctly points to the zlib specification in RFC 1950 for the "deflate" |
325 | transfer encoding, there have been reports of servers and browsers that |
327 | transfer encoding, there have been reports of servers and browsers that |
326 | incorrectly produce or expect raw deflate data per the deflate |
328 | incorrectly produce or expect raw deflate data per the deflate |
327 | specficiation in RFC 1951, most notably Microsoft. So even though the |
329 | specification in RFC 1951, most notably Microsoft. So even though the |
328 | "deflate" transfer encoding using the zlib format would be the more |
330 | "deflate" transfer encoding using the zlib format would be the more |
329 | efficient approach (and in fact exactly what the zlib format was designed |
331 | efficient approach (and in fact exactly what the zlib format was designed |
330 | for), using the "gzip" transfer encoding is probably more reliable due to |
332 | for), using the "gzip" transfer encoding is probably more reliable due to |
331 | an unfortunate choice of name on the part of the HTTP 1.1 authors. |
333 | an unfortunate choice of name on the part of the HTTP 1.1 authors. |
332 | 334 |