3.3. Content-Encoding support

DataparkSearch engine supports HTTP compression (Content encoding). Compression can have a major impact on the performance of HTTP transactions. The only way to obtain higher performance is to reduce the number of bytes transmitted.

Using content encoding to receive a server's response you can reduce the traffic by twice or more.

The HTTP 1.1 (RFC 2616) specification contains four content encoding methods: gzip, deflate, compress, and identity.

When Content-encoding is enabled, DataparkSearch's indexer sends to a server Accept-Encoding: gzip,deflate,compress string in HTTP headers.

If the server supports any of gzip, deflate or compress encoding, it sends gziped, deflated or compressed response.

To compile DataparkSearch with HTTP Content encoding support, the zlib library is required.

To enable HTTP Content encoding support, configure DataparkSearch with the following option:

./configure --with-zlib

Use this option along with all the other necessary ones.