@rest & mods - wäre es ggf. möglich die diskussion auf das zu begrezen worum es geht? und nicht wieder
einen thread zu zu heulen mit: "wäääääh chrome ist besser!!!! - derp derp ff crashed dauernd!!!!"
nur falls jemand auch gerne ne erklärung hätte was HTTP/2 eig. ist.
https://insouciant.org/tech/http-slash-2-considerations-and-tradeoffs/
http://http2.github.io/faq/#who-is-doing-this
http://blog.httpwatch.com/2015/01/16/a-simple-performance-comparison-of-https-spdy-and-http2/
What are the key differences to HTTP/1.x?
At a high level, HTTP/2:
is binary, instead of textual
is fully multiplexed, instead of ordered and blocking
can therefore use one connection for parallelism
uses header compression to reduce overhead
allows servers to “push” responses proactively into client caches
Why is HTTP/2 binary?
Binary protocols are more efficient to parse, more compact “on the wire”, and most importantly,
they are much less error-prone, compared to textual protocols like HTTP/1.x, because they often
have a number of affordances to “help” with things like whitespace handling, capitalization, line
endings, blank links and so on.
For example, HTTP/1.1 defines four different ways to parse a message; in HTTP/2, there’s just one code path.
It’s true that HTTP/2 isn’t usable through telnet, but we already have some tool support, such as a
Wireshark plugin
Why just one TCP connection?
With HTTP/1, browsers open between four and eight connections per origin. Since many sites use
multiple origins, this could mean that a single page load opens more than thirty connections.
One application opening so many connections simultaneously breaks a lot of the assumptions that
TCP was built upon; since each connection will start a flood of data in the response, there’s a real
risk that buffers in the intervening network will overflow, causing a congestion event and retransmits.
Additionally, using so many connections unfairly monopolizes network resources, “stealing” them
from other, better-behaved applications (e.g., VoIP)
Does HTTP/2 require encryption?
No. After extensive discussion, the Working Group did not have consensus to require the use of
encryption (e.g., TLS) for the new protocol.
However, some implementations have stated that they will only support HTTP/2 when it is used
over an encrypted connection.
.
.
