HTTP / 2 (h2-14, spdy4) in Google Chrome 40
It is finished!
Open: chrome: // net-internals / # spdy, and look.
Obviously (?), Due to the fact that the court in February, and as you know, as an RFC , HTTP / 2 was supposed to be just in February.
')
So far, I have noticed only on some Google services, such as mail.google.com, and so far I have clicked on the keys and the main one with the rest of the services pulled up.
It seems that now the development will go a little faster.
Yandex wrote today how they implemented TLS (with SPDY). Good match.
I consider this event to be very significant, and to all those who are still skeptical about this all (what a fig topic of a person in the red, I, honestly, do not understand at all) - reread it all, to understand that no one as a panacea offers, at least freebie to reduce the number of handshake - is it really bad?
What is the difference from spdy 3.1 (basic), this is a special HPACK compression algorithm instead of DEFLATE.
I hope the assumptions that nginx will start adding support after the RFC will soon come true. SPDY 3.1 it supports now, 4 letters in the config.
Forgiveness for the brevity and some confusion, but it just has to be here today.
I consider all this the most important movement in http and web lately.
Open: chrome: // net-internals / # spdy, and look.
Obviously (?), Due to the fact that the court in February, and as you know, as an RFC , HTTP / 2 was supposed to be just in February.
')
So far, I have noticed only on some Google services, such as mail.google.com, and so far I have clicked on the keys and the main one with the rest of the services pulled up.
It seems that now the development will go a little faster.
Yandex wrote today how they implemented TLS (with SPDY). Good match.
I consider this event to be very significant, and to all those who are still skeptical about this all (what a fig topic of a person in the red, I, honestly, do not understand at all) - reread it all, to understand that no one as a panacea offers, at least freebie to reduce the number of handshake - is it really bad?
What is the difference from spdy 3.1 (basic), this is a special HPACK compression algorithm instead of DEFLATE.
I hope the assumptions that nginx will start adding support after the RFC will soon come true. SPDY 3.1 it supports now, 4 letters in the config.
Forgiveness for the brevity and some confusion, but it just has to be here today.
I consider all this the most important movement in http and web lately.
Source: https://habr.com/ru/post/249957/
All Articles