Http2 explained

Re:Http2 explained by stusmall on Thursday February 12, 2015 @03:31PM (#9041201)

"Some of the bigger players in the HTTP field have been missing from the working group discussions and meetings. I don't want to mention any particular company or product names here, but clearly some actors on the Internet today seem to be confident that IETF will do good without these companies being involved..."

I haven't been following this much, who is he referring to?

[ Parent | on HN ]

Re:Http2 explained by bch on Thursday February 12, 2015 @04:17PM (#9041438)

> "clearly some actors on the Internet today seem to be confident that IETF will do good without these companies being involved"

That's impossible to believe. Now I wonder -- what's the _real_ reason ?

[ Parent | on HN ]

Re:Http2 explained by mongol on Thursday February 12, 2015 @03:52PM (#9041315)

Probably Apple, there is another mention of them later on in the document.

[ Parent | on HN ]

Re:Http2 explained by bsdetector on Thursday February 12, 2015 @06:48PM (#9042105)

Could be. Mobile Safari uses pipelining, so for Apple there's not a lot of benefit from HTTP2. It isn't a big enough deal for them to push a new protocol, like it is to say Google that doesn't have pipelining in their browser.

[ Parent | on HN ]

Re:Http2 explained by bagder on Thursday February 12, 2015 @07:01PM (#9042148)

Sorry, but that doesn't make a lot of sense. Pipelining is far from a replacement for HTTP/2 as the document explains a bit. Besides, Safari already supports SPDY because of this.

[ Parent | on HN ]

Re:Http2 explained by billyhoffman on Friday February 13, 2015 @01:04AM (#9043130)

Apple has already committed to (and rolled out support for) SPDY. If you have iOS8, your Mobile Safari can use SPDY. Presumablely they will shift to HTTP/2 as well.

http://zoompf.com/blog/2014/06/spdy-coming-to-safari-future-...

[ Parent | on HN ]