3 ms·
That's not true. HTTP/2.0 (or at least the successor to HTTP/1.1) has been discussed for over a decade, there have been many OS releases since then! Inventing
by joosters 13y ago
That's not true. HTTP/2.0 (or at least the successor to HTTP/1.1) has been discussed for over a decade, there have been many OS releases since then!
Inventing a whole new protocol to overcome a TCP deficiency is IMO a terrible motive...
- pritambaral 13y agoThese guys have something to say about that: http://blog.chromium.org/2013/06/experimenting-with-quic.html http://blog.chromium.org/2013/06/experimenting-with-quic.htm... A new protocol that runs on UDP precisely to side-step slow TCP changes.
- nly 13y agoThat's great, but it means it'll always be a userland library rather than a OS supported networking protocol... which means the API will never be a defacto standard akin to the BSD sockets API. The reference implementation is also in obtuse looking C++... which will hinder bindings to other languages. In short, don't expect to see this outside of Android or Chrome. On the plus side, this is exactly what UDP was for in the first place.