Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.compression > #1518

Re: Employing a set of data files guaranteed to be available at the time of decompression

Show all headers | View raw

Jim Leonard wrote:
) On Monday, September 3, 2012 9:03:14 PM UTC-5, David wrote:
)> In particular, gzip has a sliding window of 32KB, and bzip2 has a sliding window of 900KB.
)
) To clarify, bzip2 has a 900KB block size, not a 900KB sliding window.
) Each block is independent, which was by design as the author wanted file
) damage to be limited to the area of damage, and not bork everything from
) that point forward.

The fact that each block is independent is inherent in the underlying
algorithm (block-sorting).

The choice for 900KB was a bit arbitrary, it seems.


SaSW, Willem
-- 
Disclaimer: I am in no way responsible for any of the statements
            made in the above text. For all I know I might be
            drugged or something..
            No I'm not paranoid. You all think I'm paranoid, don't you !
#EOT

Back to comp.compression | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: Employing a set of data files guaranteed to be available at the time of decompression David <davidcary2@gmail.com> - 2012-09-03 19:03 -0700
  Re: Employing a set of data files guaranteed to be available at the time of decompression Industrial One <industrial_one@hotmail.com> - 2012-09-09 09:23 -0700
  Re: Employing a set of data files guaranteed to be available at the time of decompression Jim Leonard <MobyGamer@gmail.com> - 2012-09-18 14:25 -0700
    Re: Employing a set of data files guaranteed to be available at the time of decompression Willem <willem@turtle.stack.nl> - 2012-09-19 08:54 +0000

csiph-web