dolysis
/
snappy
mirror of https://github.com/google/snappy.git
3
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

In the format description, use a clearer example to emphasize that varints are 

stored in little-endian. Patch from Christian von Roques.

R=csilvers


git-svn-id: https://snappy.googlecode.com/svn/trunk@51 03e5f5b5-db94-4691-08a0-1a8bf15f6143
This commit is contained in:
snappy.mirrorbot@gmail.com 2011-10-05 12:27:12 +00:00
parent 21a2e4f557
commit b61134bc0a
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
format_description.txt
View File

@ -1,5 +1,5 @@
Snappy compressed format description Snappy compressed format description
Last revised: 2011-08-09 Last revised: 2011-10-05
This is not a formal specification, but should suffice to explain most This is not a formal specification, but should suffice to explain most
@ -21,8 +21,8 @@ The stream starts with the uncompressed length (up to a maximum of 2^32 - 1),
stored as a little-endian varint. Varints consist of a series of bytes, stored as a little-endian varint. Varints consist of a series of bytes,
where the lower 7 bits are data and the upper bit is set iff there are where the lower 7 bits are data and the upper bit is set iff there are
more bytes to be read. In other words, an uncompressed length of 64 would more bytes to be read. In other words, an uncompressed length of 64 would
be stored as 0x40, and an uncompressed length of 2097151 (0x1FFFFF) be stored as 0x40, and an uncompressed length of 2097150 (0x1FFFFE)
would be stored as 0xFF 0xFF 0x7F. would be stored as 0xFE 0xFF 0x7F.
2. The compressed stream itself 2. The compressed stream itself