Gzip/RESTXQ

Hi All,

I am wondering whether for RESTXQ one should enable gzip encoding to improve data transmission: if the database is used for storage (where the data are in binary form), is the gzip option still useful?

Best, Joseph

Hi joseph,

Compression is always useful if you transfer data that can still be reduced in size. In other words, if you store JPG files, compression won’t help so much, but it will surely shrink JSON or WAV files.

Cheers, Christian

There is some point at which the time it takes to compress is worse in some measure than serving uncompressed data.

What I did was store precompressed data and serve that, instead of enabling compression. So if that is an option you can use:

web:response-header(map {'media-type': 'application/wordstar'}, map {'Content-Encoding': 'gzip'}) , db:retrieve('test-binary', 'out.bin')

where out.bin contains gzipped data.

The web server might then serve the compressed data if Accept-Encoding contains deflate or gzip

Kendall

Hi joseph,

Compression is always useful if you transfer data that can still be reduced in size. In other words, if you store JPG files, compression won’t help so much, but it will surely shrink JSON or WAV files.

Cheers, Christian

Hello Kendall,

I have to go off-topic here for once, because it caught my eye and I couldn't believe it: wordstar? Really? And I thought working with XML is sometimes an ancient technology, but wordstar is... well, let's call it well-established ;) Or are you working for George R.R. Martin (see http://grrm.livejournal.com/197075.html), and if so how will Game Of Thrones end? ;)

I am glad to see that XQuery is really a technology used for all kind of data formats...

Cheers

Dirk

Hi Kendall,

Thanks for that. Just a question: can the compressed data on your server be searched if a RESTXQ function is supposed to perform a simple query on them before serving? Thanks.

Best, Joseph

There is some point at which the time it takes to compress is worse in some measure than serving uncompressed data.

What I did was store precompressed data and serve that, instead of enabling compression. So if that is an option you can use:

web:response-header(map {'media-type': 'application/wordstar'}, map {'Content-Encoding': 'gzip'}) , db:retrieve('test-binary', 'out.bin')

where out.bin contains gzipped data.

The web server might then serve the compressed data if Accept-Encoding contains deflate or gzip

Kendall

Hi joseph,

Compression is always useful if you transfer data that can still be reduced in size. In other words, if you store JPG files, compression won’t help so much, but it will surely shrink JSON or WAV files.

Cheers, Christian

I was kidding. Yes wordstar was great. My mother used troff as a typist back then.

Kendall

Hi Kendall,

Thanks for that. Just a question: can the compressed data on your server be searched if a RESTXQ function is supposed to perform a simple query on them before serving? Thanks.

Best, Joseph

There is some point at which the time it takes to compress is worse in some measure than serving uncompressed data.

What I did was store precompressed data and serve that, instead of enabling compression. So if that is an option you can use:

web:response-header(map {'media-type': 'application/wordstar'}, map {'Content-Encoding': 'gzip'}) , db:retrieve('test-binary', 'out.bin')

where out.bin contains gzipped data.

The web server might then serve the compressed data if Accept-Encoding contains deflate or gzip

Kendall

Hi joseph,

Compression is always useful if you transfer data that can still be reduced in size. In other words, if you store JPG files, compression won’t help so much, but it will surely shrink JSON or WAV files.

Cheers, Christian

As far as I know you have to explicitly decompress and search through the content. For example:

Kendall

Hi Kendall,

Thanks for that. Just a question: can the compressed data on your server be searched if a RESTXQ function is supposed to perform a simple query on them before serving? Thanks.

Best, Joseph

There is some point at which the time it takes to compress is worse in some measure than serving uncompressed data.

What I did was store precompressed data and serve that, instead of enabling compression. So if that is an option you can use:

web:response-header(map {'media-type': 'application/wordstar'}, map {'Content-Encoding': 'gzip'}) , db:retrieve('test-binary', 'out.bin')

where out.bin contains gzipped data.

The web server might then serve the compressed data if Accept-Encoding contains deflate or gzip

Kendall

Hi joseph,

Compression is always useful if you transfer data that can still be reduced in size. In other words, if you store JPG files, compression won’t help so much, but it will surely shrink JSON or WAV files.

Cheers, Christian