aboutsummaryrefslogtreecommitdiffstats
path: root/doc/manual/compression.rst
Commit message (Collapse)AuthorAgeFilesLines
* Reorg documentation layout. Rename manual to handbook.Jack Lloyd2019-05-311-90/+0
|
* Spell check the documentationJack Lloyd2018-09-281-1/+1
|
* Update manual to avoid use of old integer typedefs.Jack Lloyd2017-11-141-4/+4
|
* Small documentation updatesJack Lloyd2016-12-301-1/+3
| | | | [ci skip]
* Remove Transform base classJack Lloyd2016-04-211-27/+63
| | | | | | | | | | | | | | | | | | | | | | With sufficient squinting, Transform provided an abstract base interface that covered both cipher modes and compression algorithms. However it mapped on neither of them particularly well. In addition this API had the same problem that has made me dislike the Pipe/Filter API: given a Transform&, what does it do when you put bits in? Maybe it encrypts. Maybe it compresses. It's a floor wax and a dessert topping! Currently the Cipher_Mode interface is left mostly unchanged, with the APIs previously on Transform just moved down the type hierarchy. I think there are some definite improvements possible here, wrt handling of in-place encryption, but left for a later commit. The compression API is split into two types, Compression_Algorithm and Decompression_Algorithm. Compression_Algorithm's start() call takes the compression level, allowing varying compressions with a single object. And flushing the compression state is moved to a bool param on `Compression_Algorithm::update`. All the nonsense WRT compression algorithms having zero length nonces, input granularity rules, etc as a result of using the Transform interface goes away.
* Update compression docslloyd2015-05-101-0/+52