http://www.theverge.com/2016/1/20/10797268/googles-new-algorithm-chrome-run-faster?1453311003892=1 http://dlvr.it/DKrnPt Good news for chrome users.
It's also coming for Firefox 44 (https://wiki.mozilla.org/Features/Release_Tracking) And i had quick glance at it, and it looks like this compression only works for https, and if websites configure it in their servers.
If it would be bundled in Chromium update it will be available then for all Chromium-based browsers, I think.
If I remember correctly, the chrome version on android can also use data compression. It however comes at a cost to privacy as all the traffic is rerouted through their servers so it can be compressed. For the desktop version chrome used a extension, that too was a caveat to privacy. How is this exactly being implemented? Is the traffic getting re-routed then compressed or is it getting compressed natively on the fly, without being routed through their servers?
Here is my response... So, in plain terms, it only works for https sites. And website owners have to configure their webserver, for the site to work (not a big deal though). There will not be any re-routing or like that.When a user request a webpage, the webserver will compress and send the response back..
Irony is that, this algorithm is created by Google team. However, the first browser being used it will be Firefox v44 (being released in a week). And Chrome will have it on v49, in the next month
If its not going through their servers, then im okay with it. I see the advantages, many more websites will adopt HTTPS, particularly sites that have a high demand/throughput in their servers. The cost savings may be huge, not to mention the security benefits that it entails. Firefox running it first , that is strange.
This is why i use Firefox with uBlock Origin (with images disabled by default)..to save bandwidth and clear the clutter.. Yes. Its a Win-Win situation. And more reason for web-site owners to offer https..
