Timeline for Avoid double compression of resources
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 28, 2014 at 13:46 | comment | added | Russell Borogove |
Relatively, yes. I don't know what heuristics typical .zip compressors use to choose a block's encoding, but it might be as straightforward as trying all the encodings and keeping the best result. During development, if you must have your data in a .zip, you'll probably want to force everything to use store instead of deflate to save time, then deflate everything for release builds.
|
|
| May 28, 2014 at 12:07 | comment | added | Criticizing Israel not allowed | Would the compression end take a long time to realise that the file isn't compressible? | |
| May 27, 2014 at 18:27 | comment | added | aaaaaaaaaaaa | Sometimes it is that simple, a perceived problem isn't necessarily a real problem. Even if there actually was the overhead of decompressing twice, uncompressing deflate is a really quick operation, I guess the overhead would only just be measurable. | |
| May 27, 2014 at 17:08 | history | answered | Russell Borogove | CC BY-SA 3.0 |