Linked by Thom Holwerda on Fri 6th Jan 2012 17:47 UTC
Thread beginning with comment 502483
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
SPDY will be adopted by Firefox and is actually a good thing.
It helps solve the Bufferbloat problem too: http://www.youtube.com/watch?v=qbIozKVz73g
SPDY is not good in the sense that with Google Services Chrome looks like it is faster.
How is that not good?
Chrome kinda uses it secretly, which means things like gmail etc run faster than they do in other browsers.
Again, how is that not good?
Yeah it is an "open" standard but only Google are using it.
Blame those not using it, not those that do.
Edited 2012-01-08 06:31 UTC





Member since:
2007-09-22
The last few weeks YouTube has been pushing out changes and A/B testing* changed to perfect their support for WebM/HTML5 video.
For example, if you enable html5-support for Youtube at: http://youtube.com/html5
And you visit a different site with a YouTube video enabled, it is very much possible it will be displayed in HTML5/WebM.
I've also seen that YouTube has started to enable HTTPS support.
That means that https://youtube.com/ could be the default in the future. This is to protect the login-cookie users use (used by people who upload and comment).
Only the video is downloaded over HTTP from the caching servers (it is a different domain, thus the cookie won't be sent in that case).
Also they are enabling HTTPS so they can enable the use of SPDY.
SPDY is the faster 'HTTP-transport'-method of loading pages from Google as implemented in Chrome and maybe Firefox 10, but probably Firefox 11.
* A/B testing is that certain users temporarily see the new version and other users see the original. This is to test what happends when you enable new code without impacting all users if something does not work.