I look at using bijective compression as convenient, because it doesn't need to know if a piece of data is clean or tainted before application of bijective compression, it's always a safe transformation to apply. Sure, it's a bit of coder lazyness I suppose, but it is convenient to have some types of compression that you don't have to worry about crafted or just badly mangled datastreams breaking the decompressor with mathematical certainty
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Re: The usefulness is somewhat subtle.
Date: 2006-11-30 09:03 am (UTC)The most commonly referenced Bijective Compression site is really hard to read and understand unfortunately.
I look at using bijective compression as convenient, because it doesn't need to know if a piece of data is clean or tainted before application of bijective compression, it's always a safe transformation to apply. Sure, it's a bit of coder lazyness I suppose, but it is convenient to have some types of compression that you don't have to worry about crafted or just badly mangled datastreams breaking the decompressor with mathematical certainty