3 ms·
Good compression is always helpful, another working algorithm to fill out the available spectrum of choices is a plus. Why tie it to HTTP? Most transfers are h
by mikewarot 5y ago
Good compression is always helpful, another working algorithm to fill out the available spectrum of choices is a plus.
Why tie it to HTTP? Most transfers are https, which this wouldn't help.
- gus_massa 5y agoAlso, most transfered bytes are in images and videos, so compressing the text part of html/css/js will change the total number very little.
- AlexanderTheGr8 5y agoThat's true, but extremely good algorithms to compress text/image/video already exist. Devs just don't consider using them when putting them on their web servers. I was curious whether it is possible for the protocol to automatically compress such images/videos using SOTA algorithms such as zstd.
- toast0 5y agoYes, zstd is one of the officially registered content encodings https://www.iana.org/assignments/http-parameters/http-parameters.xml#http-parameters-1 https://www.iana.org/assignments/http-parameters/http-parame... I don't know if any clients or servers support it, but it's registered. It's not going to help with images or videos though. Well it might help with bitmaps, but not as much as an image compressor would. Anything that's already compressed isn't going to get smaller with a general purpose compression tool, unless the existing compression is really bad at its job. There are some purpose built compression tools that can recompress specific formats for smaller results, the one I can remember is dropbox's lepton https://dropbox.tech/infrastructure/lepton-image-compression-saving-22-losslessly-from-images-at-15mbs https://dropbox.tech/infrastructure/lepton-image-compression...