couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Davis <paul.joseph.da...@gmail.com>
Subject Re: question about how write_header works
Date Thu, 23 Sep 2010 15:55:34 GMT
On Thu, Sep 23, 2010 at 11:37 AM, Randall Leeds <randall.leeds@gmail.com> wrote:
> On Thu, Sep 23, 2010 at 15:44, Paul Davis <paul.joseph.davis@gmail.com> 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.
>

Oh forgot to mention that. And yep, its 4K.

Mime
View raw message