HTTP Intermediary Layer From Google Could Dramatically Speed Up the Web
grmoc writes "As part of the 'Let's make the web faster' initiative, we (a few engineers — including me! — at Google, and hopefully people all across the community soon!) are experimenting with alternative protocols to help reduce the latency of Web pages. One of these experiments is SPDY (pronounced 'SPeeDY'), an application-layer protocol (essentially a shim between HTTP and the bits on the wire) for transporting content over the web, designed specifically for minimal latency. In addition to a rough specification for the protocol, we have hacked SPDY into the Google Chrome browser (because it's what we're familiar with) and a simple server testbed. Using these hacked up bits, we compared the performance of many of the top 25 and top 300 websites over both HTTP and SPDY, and have observed those pages load, on average, about twice as fast using SPDY. Thats not bad! We hope to engage the open source community to contribute ideas, feedback, code (we've open sourced the protocol, etc!), and test results."
Now we can see Uncle Goatse twice as fast.
In the future, the content will be loaded before you click! Unfortunately, it's not like it today, so I didn't make the first post...
How is this different from Web servers that serve up gzipped pages?
If only the Google engineers can do something about Slashdot's atrociously slow Javascript. Like maybe they can remove the sleep() statements.
What, just because the original poster pulls a "look at me, I did something cool, therefore I must be cool!" doesn't mean I have to go along with it.
You can generally surf the web ten times or faster if you just
1) Turn off image loading
2) Turn off Javascript
3) Turn off Java
4) Turn off plugins
yeah, yeah... I know... It's called "lynx"
And all other "add this piece of Javascript to your Web page and make it more awesomer!"
Yes, yes, they're useful. And you can't fathom a future without them. But in the meantime I'm watching my status bar say, "completed 4 of 5 items", then change to "completed 11 of 27 items", to "completed 18 of 57 items", to "completed... oh screw this, you're downloading the whole Internet, just sit back, relax and watch the blinkenlights".
Remember when a 768kbps DSL line was whizzo fast? Because all it had to download was some simple HTML, maybe some gifs?
I want my old Internet back. And a pony.
That's why smart web developers put those scripts at the end of the body.
So if Google sped up the non-ad web, they would have more room for their ads?
SNEAKY!!
I think you mean SNKY
You could also remove images, CSS, Javascript, and text, imagine the time savings!
"Our two-party system is like a bowl of shit looking at itself in a mirror." - Lewis Black
oldermanwholikestofondleyou.cx
To follow the goatse.cx standard, I believe it should be http://oldermanwholikestofondleyour.co.ck
It's only $250 to register a .co.ck address!
Remove the content too. It's all meaningless stuff like this post.
we need some stupid idealistic programmer to do the work we dont want [to do, to spend on, etc]
So save the CSS to your HD and put a filter in an extension/proxy/etc to replace the CSS URL with your local file. Wait, isn't that what the cache is for? Hmm...
Dilbert RSS feed
If they really wanted a faster web, they would have minimized the protocol name. Taking out vowels isn't enough.
The protocol should be renamed to just 's'.
That's 3 less bytes per request.
I can haz goolge internship?
I heard of a program called DeCSS. Maybe that's what it does!
You are in a maze of twisty little passages, all alike.