From: Eric Cooper <ecc@cmu.edu>
To: caml-list@inria.fr
Subject: integration of compression with channels
Date: Tue, 4 Nov 2008 07:50:20 -0500 [thread overview]
Message-ID: <20081104125019.GA5817@localhost> (raw)
I was interested to see Zack's work on integrating gzip and bzip2 with
I/O channels:
http://upsilon.cc/~zack/blog/posts/2008/11/ocaml_batteries_gzip/
I initially tried something like this in the approx proxy server, but
found out the hard way that it was difficult to deal with corrupt .gz
files. You might only discover the corruption after reading garbage
for a while, and an exception at that point would be unexpected.
Eventually I switched to spawning a "gunzip" process to a temporary
file, and then reading that. In addition to detecting corruption
early, it was also significantly faster than CamlZip.
I suppose one could argue that you can get an I/O error even from
reading an uncompressed file (bad disk block, or whatever), and that
a robust program should be equally prepared to deal with that.
But I think there's a real difference in practice.
The integrated approach is definitely more elegant, and perhaps the
performance will be competitive someday. So I'd be interested
if anyone has a better way of handling potentially corrupt files.
--
Eric Cooper e c c @ c m u . e d u
next reply other threads:[~2008-11-04 12:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 12:50 Eric Cooper [this message]
2008-11-04 13:26 ` [Caml-list] " Stefano Zacchiroli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081104125019.GA5817@localhost \
--to=ecc@cmu.edu \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox