Google's SPDY protocol will speed up the web - and Chrome OS, too
Over at the Chromium blog, Google has announced a project they've been working on called 'SPeeDY.' It's an updated transport protocol for the web which improves upon HTTP, reducing latency through network-fu like multiplexed streams, request prioritization, and header compression.
"We started working on SPDY while exploring ways to optimize the way browsers and servers communicate," says the official blog post. It continues, "We want to continue building on the web's tradition of experimentation and optimization, to further support the evolution of websites and browsers."
It's not all about altruism, of course. Improvements like those Google is seeking with SPDY, the Go! programming language, and Native Client will all greatly benefit the Chrome browser and Chrome OS. After all, an OS which relies heavily on the cloud for access apps and data will certainly perform better with an improved protocol powering the client and server. It's probably a safe bet that Google would roll SPDY on their own servers early on to give apps like Google Docs and Picasa Web a performance boost on the Google platform.
Whatever the motivation, I'm all for more speed on the web. My ISP is obviously in no hurry to improve things on that front, so if Google can pull off the estimated 55% performance gain then I'm all for it. You go, Google!
"We started working on SPDY while exploring ways to optimize the way browsers and servers communicate," says the official blog post. It continues, "We want to continue building on the web's tradition of experimentation and optimization, to further support the evolution of websites and browsers."
It's not all about altruism, of course. Improvements like those Google is seeking with SPDY, the Go! programming language, and Native Client will all greatly benefit the Chrome browser and Chrome OS. After all, an OS which relies heavily on the cloud for access apps and data will certainly perform better with an improved protocol powering the client and server. It's probably a safe bet that Google would roll SPDY on their own servers early on to give apps like Google Docs and Picasa Web a performance boost on the Google platform.
Whatever the motivation, I'm all for more speed on the web. My ISP is obviously in no hurry to improve things on that front, so if Google can pull off the estimated 55% performance gain then I'm all for it. You go, Google!













Comments
9
Subscribe to commentsCamNov 12th 2009 4:45PM
So can Google get rid of the // now?
spdy:thisisaurlhere.com ?
Kris120890Nov 12th 2009 4:53PM
Is this going to take years and would this require all sites to change they build their websites or is it as simple as just modifying parts of the website. As you can tell I'm not clued up exactly on this kind of thing even though I use it everyday.
Kris120890Nov 12th 2009 4:59PM
Also, about halfway down there is a comment from Mike beltzner. He is the head guy at Mozilla right. So this would mean Chrome and firefox would be ready at similar times if this ever goes ahead and gets accepted.
CamNov 12th 2009 5:02PM
My guess is that http will stick around for a bit, some sites will move completely to spdy, while some will be accessible through spdy and http, and some will stay http. I don't see it replacing http completely.
der_tuxmanNov 12th 2009 5:04PM
No, SPDY will not speed up anything. HTTP already knows the "If-Modified-Since" instruction. SPDY basically says that even non-modified content should be downloaded while requesting HTTP headers, so they are available instantly. You see, this is like turning off your browser cache.
It might be a way to avoid Google Adsense to be blocked, but it is not an improvement in any way.
Bullshit!
StevenNov 13th 2009 1:37PM
Wow...it's obvious that you haven't read the documents on the SPDY site.
der_tuxmanNov 13th 2009 1:39PM
It's obvious that you have read them but did not understand what it is about...
der_tuxmanNov 12th 2009 5:08PM
BTW, there's no point in compressing HTTP headers. It would mean that the web server has to work a lot more. Now guess what that means for your reliability. A server is not a fucking workstation! Ah, Google makes me puke.
StevenNov 13th 2009 1:37PM
"Go!" is the language that Google didn't invent. go is the language they did invent.