43 replies to this topic

[still1]

Quote

If there's anything that Google doesn't like, it's things that collect dust. The company is famous for its annual spring cleaning efforts, in which the firm rids itself of redundant and dead-end projects, along with more bullish moves, such as its push to overhaul the internet's DNS system. Now it's looking to replace HTTP with a new protocol known as SPDY, and to that end, it's demonstrating the potential speed gains that one might expect on a mobile network. According to the company's benchmarks, mean page load times on the Galaxy Nexus are 23 percent faster with the new system, and it hypothesizes that further optimizations can be made for 3G and 4G networks. To its credit, Google has already implemented SPDY in Chrome, and the same is true for Firefox and Amazon Silk. Even Microsoft appears to be on-board. As a means to transition, the company proposes an Apache 2.2 module known as mod_spdy, which allows web servers to take advantage of features such as stream multiplexing and header compression. As for HTTP, it's no doubt been a reliable companion, but it seems that it'll need to work a bit harder to earn its keep. Stay weird, Google, the internet wouldn't be the same without you.

http://www.engadget....dy-replacement/

[+Brando212]

interesting

[HawkMan]

It's a food thing we can measure things down to the millisecond so we can pretend this actually makes a difference.

[+remixedcat]

a food thing???

[Ambroos]

If you use Google Chrome you have actually been using it for ages. Most Google.com-based sites (Gmail, Search, ...) and Twitter all use SPDY automatically when using HTTPS.

To see when you're on a SPDY-powered site: use https://chrome.googl...jhmgnchggcjblin

[TRC]

It doesn't replace HTTP, it works with it. The name makes me cringe though.

[hjf288]

The multiplexing is actually quite nice..

[+Brando212]

Ambroos, on 02 May 2012 - 21:19, said:

If you use Google Chrome you have actually been using it for ages. Most Google.com-based sites (Gmail, Search, ...) and Twitter all use SPDY automatically when using HTTPS.

To see when you're on a SPDY-powered site: use https://chrome.googl...jhmgnchggcjblin

it's available for firefox as well https://addons.mozil...dicator/?src=ss

[still1]

Ambroos, on 02 May 2012 - 21:19, said:

If you use Google Chrome you have actually been using it for ages. Most Google.com-based sites (Gmail, Search, ...) and Twitter all use SPDY automatically when using HTTPS.

To see when you're on a SPDY-powered site: use https://chrome.googl...jhmgnchggcjblin

Brando212, on 02 May 2012 - 21:23, said:

it's available for firefox as well https://addons.mozil...dicator/?src=ss

Microsoft is implementing SPDY too.. hopefully in IE10

Quote

How?
The HTTP Speed+Mobility proposal starts from both the Google SPDY protocol (a separate submission to the IETF for this discussion) and the work the industry has done around WebSockets.
SPDY has done a great job raising awareness of web performance and taking a “clean slate” approach to improving HTTP to make the Web faster. The main departures from SPDY are to address the needs of mobile devices and applications.

http://blogs.msdn.co...web-faster.aspx

[bogas04]

remixedcat, on 02 May 2012 - 21:12, said:

a food thing???

foolish probably ?

Ambroos, on 02 May 2012 - 21:19, said:

If you use Google Chrome you have actually been using it for ages. Most Google.com-based sites (Gmail, Search, ...) and Twitter all use SPDY automatically when using HTTPS.

To see when you're on a SPDY-powered site: use https://chrome.googl...jhmgnchggcjblin

And its now supported by Firefox(Beta) too ! And to check if site uses SPDY use https://addons.mozil...tor/?src=search (as told above)

[+Phouchg]

But of course HTTP is crap. Internets was never meant to be whatever it is now and what it will in an increasing pace continue to be evolved. Sometimes makes me wonder - didn't anybody see that s*it was going overboard really quickly and think "better pull the plug, it's gonna blow".

Good luck on replacing HTTP, and DNS, too, though. Then while they're at it, might as well replace HTML, too. It's all too widespread and fundamental.

[still1]

Phouchg, on 02 May 2012 - 21:53, said:

But of course HTTP is crap. Internets was never meant to be whatever it is now and what it will in an increasing pace continue to be evolved. Sometimes makes me wonder - didn't anybody see that s*it was going overboard really quickly and think "better pull the plug, it's gonna blow".

Good luck on replacing HTTP, and DNS, too, though. Then while they're at it, might as well replace HTML, too. It's all too widespread and fundamental.

SPDY does not replace HTTP; it modifies the way HTTP requests and responses are sent over the wire.^[1] This means that all the existing server-side applications can be used without modification if a SPDY-compatible translation layer is put in place.

http://en.wikipedia.org/wiki/SPDY

[abecedarian paradoxious]

Phouchg, on 02 May 2012 - 21:53, said:

But of course HTTP is crap. Internets was never meant to be whatever it is now and what it will in an increasing pace continue to be evolved. Sometimes makes me wonder - didn't anybody see that s*it was going overboard really quickly and think "better pull the plug, it's gonna blow".

Good luck on replacing HTTP, and DNS, too, though. Then while they're at it, might as well replace HTML, too. It's all too widespread and fundamental.

What's another proprietary standard?

[Salty Wagyu]

Can be enabled in firefox by toggling network.http.spdy.enabled in about:config

And the SPDY indicator addon: https://addons.mozil...spdy-indicator/

[Singh400]

Lemme guess Google owns the rights to SPDY.