New HTTP protocol from Google

Server NGINX
1

Hey,
please don’t see this as a feature request - I just wanted to inform
those who’ve missed the news about SPDY, an interesting new
alternative protocol to HTTP. There are of course a plethora of
alternatives even in this part of development, but this actually has
code you (soon) can compile for yourself.

Have a look see:

Cheers,
Johan

2

On Fri, Nov 13, 2009 at 09:26:38AM +0100, Johan Bergström wrote:

Hey,
please don’t see this as a feature request - I just wanted to inform
those who’ve missed the news about SPDY, an interesting new
alternative protocol to HTTP. There are of course a plethora of
alternatives even in this part of development, but this actually has
code you (soon) can compile for yourself.

Have a look see: SPDY: An experimental protocol for a faster web - The Chromium Projects

What I do not like in this: a binary protocol like FastCGI. It means you
can not use netcat or telnet to test something. You need some tool like
“openssl s_client …” to talk a server.

3

i was asking myself: does it really require any change on the server
side?

Am 13.11.2009 09:26, schrieb Johan
Bergström:> Hey,

4

On Fri, Nov 13, 2009 at 09:58:10AM +0100, Omar Abo-Namous wrote:

i was asking myself: does it really require any change on the server side?

Yes. A lot of changes.

5

Google should stop trying to conquer the world, it has already lost
its original appeal and it’s following the path to the Dark Side…
Sad. So what’s next, Google’s HTTP vs everyone else’s? :wink: Kinda
reminds me of IE vs Netscape, you would’ve thought they’d learnt by
now…

Meh… random damblings… (from someone using a google account)

6

People, read some more about that new protocol. Google has found in a
way the golden middle by improving the speed and at the same time keep
the TCP so that you do not need to buy new routers, etc in order to
get the benefits. So say nginx implements the “new HTTP” and you are
using Chrome, you will get the benefits. But if the server is on IIS
then you will still use “old HTTP” because the server still does not
support that protocol. Simple as that, so sites which care about speed
will upgrade/change their server software (I am sure apache will
implement it fairly quickly).

Thank Google that they care about speed and increasing the throughput.
Small companies cannot make radical changes, so you need to big
companies to lead the way.

2009/11/13 Nuno Magalhães [email protected]:

7

Johan Bergström ha scritto:

Hey,
please don’t see this as a feature request - I just wanted to inform
those who’ve missed the news about SPDY, an interesting new alternative
protocol to HTTP. There are of course a plethora of alternatives even in
this part of development, but this actually has code you (soon) can
compile for yourself.

Google should really try to improve existing standards instead of
inventing new things.

Some of the more interesting features can be implemented in HTTP, IMHO.
As an example, header compression, using the Trailer header:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.40

Headers that need to be compressed can be specified in the Trailer
header.

[…]

Regards Manlio