XBLOCKS are currently detected by the first two bytes of data both being 1.
They should be detected by first testing the 0x02 bit of the block id and only
if it is set, checking the first two bytes of data.
This would only be a problem if a data block that wasn't an XBLOCK (array)
started with two 1s.
XXBLOCKS aren't handled at all. Since XXBLOCKS describe very large amounts of
data, I propose that the api should provide some kind of stream to access them
rather than trying to read extremely large amounts of data into memory as is
done in the case of XBLOCKs (arrays) and likely running out of memory!
Original issue reported on code.google.com by orin.e...@gmail.com on 12 Aug 2010 at 1:23
Original issue reported on code.google.com by
orin.e...@gmail.com
on 12 Aug 2010 at 1:23