News for hackers. Stuff that matters.
Re:Making HTTP realtime with HTTP 2.0 by jimktrains2 on Sunday October 20, 2013 @07:59PM (#6582172)
I just feel like the basic idea of HTTP 2.0 misses the point of a stateless, text-based protocol. Also, muxing, flowcontrol? These are not things application level protocols should be caring about.
Re:Making HTTP realtime with HTTP 2.0 by X-Cubed on Sunday October 20, 2013 @08:14PM (#6582242)
It does miss the point of a stateless, text-based protocol but only because that's core to the problems currently experienced in HTTP/1.1 that are identified near the start of the presentation.

The nice thing about this approach is that it is entirely contained such that the web application in the browser doesn't know (or even need to know) the difference, in the same way that current web applications don't need to worry about whether the request data was compressed or not.

Re:Making HTTP realtime with HTTP 2.0 by comex on Sunday October 20, 2013 @08:21PM (#6582268)
Certainly, there are plenty of things in HTTP 2.0 that make sense to be there, such as server push, specialized header compression, etc.

However, some things, such as avoiding making multiple connections due to congestion and due to slow-start being slow, flow control, and arguably encryption, seem like they would be better addressed in TCP. And in fact, Google is trying to do that with QUIC.

The problem is that if (when) those things get standardized in HTTP/2.0, they need to be supported forever, even if an improved transport layer protocol makes them obsolete in relatively short order.

Re:Making HTTP realtime with HTTP 2.0 by FooBarWidget on Monday October 21, 2013 @07:07AM (#6584652)
You can't address things in TCP. There is so much network infrastructure deployed that trying to push any non-backward compatible change in TCP is futile. Google did the right thing by addressing the problems in layer 5.
Re:Making HTTP realtime with HTTP 2.0 by comex on Monday October 21, 2013 @02:00PM (#6587156)
Then just tunnel on top of UDP, like QUIC currently does. Doesn't mean it has to be specific to one application.
Re:Making HTTP realtime with HTTP 2.0 by jimktrains2 on Sunday October 20, 2013 @08:43PM (#6582371)
Your post made me reflect a bit and I agree with you whole-heartedly. I wouldn't have such a visceral dislike of HTTP/2.0 if it didn't have the TCP-like features in it.
Re:Making HTTP realtime with HTTP 2.0 by angersock on Sunday October 20, 2013 @08:43PM (#6582372)
One wonders why the hell they're trying to fix flow-control, traffic priority, encryption, etc. in a standard meant for just moving around document.

It reeks of overengineering--might as well spend that energy improving TCP or putting together a better secure sockets layer.

Most of the problems they cite are the result of people shoving too much shit (ads, trackers, social media, etc.) into their sites anyways.

Re:Making HTTP realtime with HTTP 2.0 by FooBarWidget on Monday October 21, 2013 @07:10AM (#6584663)
It reeks of overengineering because you're not properly understanding the problem.

Flow control is necessary because it's a multiplexed protocol. Without your own flow control commands, flow control is applied over the entire TCP stream, not on your substreams. That doesn't do what you want. Try it: implement any kind of multiplexed protocol yourself, and you will quickly see why it is necessary.

Encryption: some of it might be for security, but a lot of it is also for backward compatibility. SPDY/HTTP2 is a different protocol than HTTP1, and there are a lot of broken routers out there that will break things unless you encrypt the entire connection as an SSL session.

Those who do not understand SPDY are doomed to complain about it on HN, and then one day maybe reinvent it, poorly.

Re:Making HTTP realtime with HTTP 2.0 by jimktrains2 on Monday October 21, 2013 @08:07AM (#6584910)
> Flow control is necessary because it's a multiplexed protocol. Without your own flow control commands, flow control is applied over the entire TCP stream, not on your substreams. That doesn't do what you want. Try it: implement any kind of multiplexed protocol yourself, and you will quickly see why it is necessary.

Why should HTTP be a multiplex protocol though; that's the issue.

> Encryption: some of it might be for security, but a lot of it is also for backward compatibility. SPDY/HTTP2 is a different protocol than HTTP1, and there are a lot of broken routers out there that will break things unless you encrypt the entire connection as an SSL session.

So why not just use SSL/TLS? Why wrap it into the HTTP protocol?

> Those who do not understand SPDY are doomed to complain about it on HN, and then one day maybe reinvent it, poorly.

Those who can't see the benefits and reason for HTTP1 are doomed to make a mess of it by "improving" (or "working around") it.

Re:Making HTTP realtime with HTTP 2.0 by FooBarWidget on Monday October 21, 2013 @09:43AM (#6585422)
> Why should HTTP be a multiplex protocol though; that's the issue.

Because HTTP is inefficient due to the TCP three-way handshake, and because pipelining has many problems. These are fixed by multiplexing.

> So why not just use SSL/TLS? Why wrap it into the HTTP protocol?

They are using TLS.

Re:Making HTTP realtime with HTTP 2.0 by jimktrains2 on Monday October 21, 2013 @01:29PM (#6586936)
> Because HTTP is inefficient due to the TCP three-way handshake, and because pipelining has many problems. These are fixed by multiplexing.

So why should HTTP care about this?

> They are using TLS.

But it's specified as part of the HTTP protocol

Re:Making HTTP realtime with HTTP 2.0 by shawnz on Sunday October 20, 2013 @08:37PM (#6582350)
HTTP 2.0 is a bet that those ideals don't matter anymore. If the users of HTTP disagree, it just won't be adopted, simple as that.
Re:Making HTTP realtime with HTTP 2.0 by srd on Monday October 21, 2013 @02:51AM (#6583789)
Until bosses without a low-level IT background show up and ask you why you're not expanding their buzzword bingo options.
Re:Making HTTP realtime with HTTP 2.0 by zobzu on Sunday October 20, 2013 @11:33PM (#6583151)
it fixes what google cares about