Google Cuts Chrome Page Load Times In Half w/ SPDY

An anonymous reader writes "It appears as if Google has quietly implemented the SPDY HTTP replacements in Chrome (well, we knew that), and its websites. All its websites were recently updated with SPDY features that address some of the HTTP latency issues. The result? Google says the pageload times were cut about in half. SPDY will be open source, so there is some hope that other browser manufacturers will add SPDY as well."

Comments

Re:Embrace, Extend, ?

[bmo]

No, because the Microsoft way to embrace, extend, extinguish was to keep the "how to extend" part to itself and secret, like what they did with Kerberos.

This is open sauced. You are free to implement it in your own stuff.

You would have known that if you read the article.

--
BMO

SPDY - server push

[ThePhilips]

My favorite part of the SPDY is server push: now advertisers can clog my internet channel and hog the browser with ads long before the AdBlock kicks in. Or a hacked site would host malware and load it onto potential victims harddrives in parallel to normal surfing. Imagination is the only limit - of how it can go wrong.

For the security reasons, I think SPDY is a bad thing.

And I'm personally not bothered with 1-2s loading times.

P.S. The Chrome guys instead would have invested more times in the bookmarks, to make them useful. They could start by integrating Chrome with the Google Bookmarks.