Linked by Kroc Camen on Thu 12th Nov 2009 19:30 UTC
Google Google have created a new HTTP-based protocol "SPDY" (pronounced "Speedy") to solve the problem of the client-server latency with HTTP. "We want to continue building on the web's tradition of experimentation and optimization, to further support the evolution of websites and browsers. So over the last few months, a few of us here at Google have been experimenting with new ways for web browsers and servers to speak to each other, resulting in a prototype web server and Google Chrome client with SPDY support."
E-mail Print r 2   · Read More · 65 Comment(s)
Thread beginning with comment 394384
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Downside
by cerbie on Thu 12th Nov 2009 23:42 UTC in reply to "Downside"
Member since:

...but the resources to be retransmitted are also now smaller and more efficient, helping to negate it. So, if it becomes a problem, do a little reconfiguration, and change default recommendations on new pieces of network infrastructure. The networks will adapt, if it's a problem.

If it ends up working out, it can be worked into browsers and web servers all over, and many of us can benefit. Those who don't benefit can safely ignore it, if it's implemented well. We all win. Yay.

The Real Problem we have is that old protocols have proven themselves extensible and robust. But, those protocols weren't designed to do what we're doing with them. So, if you can extend them again, wrap them in something, etc., you can gain 90% of the benefits of a superior protocol, but with easy drop-down for "legacy" systems, and easy routing through "legacy" systems. This is generally a win, when starting from proven-good tech, even if it adds layers of complexity.

Reply Parent Score: 4