On Wed, Jul 16, 2014 at 02:03:58AM -0400, John Cowan wrote:
Larry McVoy scripsit:
We tried that but the problem is that you
can't encode all the options you
want in just a character. Compression doesn't take options, the CRC/XOR
layer wants to know how big you might think the file is (because we
support blocksizes from about 256B to 256K and we want to know the
file size to guess the block size).
It's a string: you can have as many characters as you want.
I understand your desire to have one API. We tried and it just wasn't
practical. Imagine pushing an encryption layer that wants a key,
XOR layer that wants block size, etc.