I was kidding. Yes wordstar was great. My mother used troff as a typist back then.
Kendall On 2/23/17, 12:44 AM, "meumapple" <[email protected]> wrote: 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 Il giorno 23 feb 2017, alle ore 02:22, Kendall Shaw <[email protected]> ha scritto: 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 On 2/21/17, 10:53 AM, "[email protected] on behalf of Christian Grün" <[email protected] on behalf of [email protected]> wrote: Hi joseph, > 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? 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
