Hello HTTP/2, Goodbye SPDY

#1

Post by Nimi » Mon, Feb 09, 2015, 5:46 PM UTC

Hello HTTP/2, Goodbye SPDY
blog.chromium.org

Re: Hello HTTP/2, Goodbye SPDY

#2

Post by klapinat0r » Mon, Feb 09, 2015, 6:28 PM UTC

SPDY came and went before I had to implement it. Phew.

On a serious note: it's nice to see ALNP being used in HTTP/2

Re: Hello HTTP/2, Goodbye SPDY

#3

Post by jjcm » Mon, Feb 09, 2015, 6:33 PM UTC

Are there any good reverse proxies out there that support HTTP/2? Right now I'm using varnish, but I'd love to switch over to something supporting this.

Re: Hello HTTP/2, Goodbye SPDY

#4

Post by itsbits » Mon, Feb 09, 2015, 6:36 PM UTC

Hardly a surprise..

Re: Hello HTTP/2, Goodbye SPDY

#5

Post by anderspetersson » Mon, Feb 09, 2015, 6:40 PM UTC

Looking forward to when HAProxy support for HTTP/2 lands since they refused to implement SPDY support.

Here's a list of common servers support for SPDY/HTTP2: https://istlsfastyet.com/#server-performance

Re: Hello HTTP/2, Goodbye SPDY

#6

Post by fdsary » Mon, Feb 09, 2015, 6:40 PM UTC

What happens if someone built a service based on it? Should they never trust browsers keeping alive even the shitty (in comparison to free and standardised HTTP/2) features? What's great about the web is that now 20 year old services still are working in the latest runtimes (browsers).

Re: Hello HTTP/2, Goodbye SPDY

#7

Post by quonn » Mon, Feb 09, 2015, 6:43 PM UTC

fdsary wrote: post #6

What happens if someone built a service based on it? Should they never trust browsers keeping alive even the shitty (in comparison to free and standardised HTTP/2) features? What's great about the web is that now 20 year old services still are working in the latest runtimes (browsers).

The server should fall back to HTTP anyway, so this should not be a problem.

Re: Hello HTTP/2, Goodbye SPDY

#8

Post by azakai » Mon, Feb 09, 2015, 6:52 PM UTC

fdsary wrote: post #6

What happens if someone built a service based on it? Should they never trust browsers keeping alive even the shitty (in comparison to free and standardised HTTP/2) features? What's great about the web is that now 20 year old services still are working in the latest runtimes (browsers).

It is always risky to build a service based on something that is not yet standardized. SPDY was in progress to be standardized, but the process ended up with parts of it in HTTP2, making SPDY unnecessary, as I understand things.

It would be the right thing for Google to remove SPDY at this point, otherwise it would be running a nonstandard protocol that other browsers do not, which can lead to fragmentation - as we saw just recently with an API that sadly Google has not removed despite it being nonstandard (FileSystem in the WhatsApp "Web" app).

edit: To clarify, I mean what Google is doing with SPDY sounds like the right thing. I don't mean it should remove it right now, I meant it was the right thing to do, right now, to announce it would be removed after a reasonable delay (and 1 year sounds reasonable).

Re: Hello HTTP/2, Goodbye SPDY

#9

Post by dragonwriter » Mon, Feb 09, 2015, 6:58 PM UTC

azakai wrote: post #8

fdsary wrote: post #6

What happens if someone built a service based on it? Should they never trust browsers keeping alive even the shitty (in comparison to free and standardised HTTP/2) features? What's great about the web is that now 20 year old services still are working in the latest runtimes (browsers).

It is always risky to build a service based on something that is not yet standardized. SPDY was in progress to be standardized, but the process ended up with parts of it in HTTP2, making SPDY unnecessary, as I understand things. It would be the right thing for Google to remove SPDY at this point, otherwise it would be running a nonstandard protocol that other browsers do not, which can lead to fragmentation - as we s…

> SPDY was in progress to be standardized, but the process ended up with parts of it in HTTP2, making SPDY unnecessary, as I understand things.

The "progress to be standardized" for SPDY was SPDY being chosen as the basis for HTTP/2; as I understand for a while SPDY has been being updated in parallel to the HTTP/2 development work to continue to reflect the state of HTTP/2 + new things the Google SPDY team wants to get into the standard, but its been clear for a long time that the intent was that SPDY as a separate protocol would be unnecessary once HTTP/2 was ready for use.

Re: Hello HTTP/2, Goodbye SPDY

#10

Post by kozhevnikov » Mon, Feb 09, 2015, 7:01 PM UTC

azakai wrote: post #8

fdsary wrote: post #6

What happens if someone built a service based on it? Should they never trust browsers keeping alive even the shitty (in comparison to free and standardised HTTP/2) features? What's great about the web is that now 20 year old services still are working in the latest runtimes (browsers).

It is always risky to build a service based on something that is not yet standardized. SPDY was in progress to be standardized, but the process ended up with parts of it in HTTP2, making SPDY unnecessary, as I understand things. It would be the right thing for Google to remove SPDY at this point, otherwise it would be running a nonstandard protocol that other browsers do not, which can lead to fragmentation - as we s…

To be fair Google did happily kill Gears when HTML5 became a viable [early draft] standard.