Bradley L Schatz

The original AFF4 paper used Zlib compression, while in Evimetry and the Wirespeed paper we started using deflate (if I recall correctly, because the Adler32 checksum calculation was a bottleneck...

Re Lz4 - we have seen some chatter suggesting similar, but haven't been able to replicate it. In all our testing snappy is still winning. I'd like to get to...

I don't think we need to be prescriptive about which algorithm to use. The spec is silent on this.

The purpose of the patch is to enable any consumer of the c-aff4 *library* to open the Striped Canonical Reference Images. The patch doesn't load all images in the folder....

Michael, The spacing related commits make the relevant lines consistent with the wider indent style. The majority of the surrounding code uses spaces, whereas those few lines used tabs.

v1 standard @ 3.2 "Storage of uncompressed chunks is supported by the simple principle that if len(chunk) == aff4:chunk_size then it is a stored chunk." An implication of the above...

I propose updating the spec to the following: "Chunks written to the Image Stream must be of size chunkSize. When writing sub-chunkSize chunks, the remaining space must be padded with...

It isn't an optimisation. The restriction has always been there: "Image streams specify the chunk_size attribute, as the number of image bytes each chunk contains (chunk size defaults to 32...

Nicely done. Thanks!

bump++