On Thu, Sep 23, 2010 at 15:44, Paul Davis <[email protected]> wrote: > As to the header2 or header1 problem, if header2 appears to be > corrupted or is otherwise discarded, the header search just continues > through the file looking for the next valid header. In this case that > would mean that newData2 would not be considered valid data and > ignored.
It's worth noting that headers appear on specific boundaries (I don't remember offhand, but might be 4K.) Non-header data is broken across this boundary with a 0 byte so that you can even store a CouchDB file inside another CouchDB database and the code cannot mistakenly find an incorrect header.
