Discussion in 'Article Discussion' started by Gareth Halfacree, 23 Sep 2015.
Major bandwidth savings ahead.
How whould it work even for static pages? You store and serve already compressed HTML files?
Yup, and they're decompressed on-the-fly by the recipient browser. It's already possible to do this in Apache and other web servers - with Apache you'd use content negotiation and MultiViews to serve up the pre-compressed content. Basically, this wouldn't really need any changes server-side: you could just install a Brotli binary and compress your static content automagically. It just needs browsers to support decompression.
Two questions: does it use middle-out compression; and what is its Weissman score?
But you would still need to store the uncompressed files in case the client does not support Brotli, right?
Yup - or you could decompress 'em on the fly, I guess. Storage, though, is way cheaper than bandwidth. Remember that Google is an advertising firm: it creates one advert then serves that advert to a billion eyeballs. Doubling up the storage used by a 50KB advert in exchange for shaving 26 per cent off the bandwidth required by those billion impressions is a no-brainer - and makes the end-user happier, too, as the page loaded faster and they've used less battery and data allowance (both of which mean said end-user is now more likely to stay online and view even more adverts.)
No way it beats http://www.piedpiper.com/
Someone even tried it: I Hacked The Middle-Out Compression From ‘Silicon Valley’
It's never going to catch on, no one likes broccoli.
I just love Gareth's use of 'automagically'...
Separate names with a comma.