I-Google imemezele ezinsukwini ezimbalwa ezedlule sekuqalile vele ukuthunyelwa kwe-HTTP / 3 ne-IETF QUIC ku-Chrome futhi kulesi simemezelo, uthi ulindele ukuthi lokhu kubuyekezwa kulethe ukuthuthukiswa kokusebenza okwengeziwe, ikakhulukazi ngokuxhaswa kwe-QUIC.
I-QUIC yiphrothokholi entsha yokuthuthwa kwenethiwekhi ehlanganisa izici ze-TCP, i-TLS nokuningi. I-HTTP / 3 inguqulo yakamuva ye-HTTP, umthetho olandelwayo ophethe iningi lethrafikhi yewebhu. I-HTTP / 3 isebenza kuphela ku-QUIC.
I-Internet Engineering Task Force, noma i-IETF, yethule i-HTTP / 2 ngo-2015, futhi okunye kokuthuthuka okukhulu eyikwenzile ukusekela i-multiplexing.
Kodwa-ke, ibisebenzise i-TCP njengeprothokholi yezokuthutha nezindlela zokuthola ukulahleka ku-TCP, ngakho-ke amaphakethe alahlekile angadala ukubambezeleka kukho konke ukuthengiselana okusebenzayo.
Ngokwamukela i-QUIC, i-HTTP / 3 ingaqhubeka ithuthukise inqubo yokudlulisa, ngoba amaphakethe alahlekile kuleli cala athinta kuphela ukuthengiselana okuthinteka ngqo.
Eqinisweni, I-QUIC yenziwe ekuqaleni i-Google futhi okokuqala kwamenyezelwa ngonyaka we-2013. Kusukela lapho, umthetho olandelwayo ufikile eminyakeni yobudala futhi njengamanje unesibopho sokuthwala ingxenye yesithathu yethrafikhi yakwaGoogle.
Kwathi ngo-2015, ukuthuthukiswa kwe-QUIC kwadlulela ezandleni ze-IETF, okuyigungu lamazinga elibhekele ukugcinwa kwezivumelwano ze-Intanethi. IETF ithuthukise i-QUIC ngezinguquko eziningana. Kuze kube manje, kunezinqubo ezimbili ezifanayo kodwa ezihlukile, okuyilezi: I-Google QUIC ne-IETF QUIC.
I-Google imemezele ukuthi ihlale isebenzisa inguqulo yayo ye-QUIC, kepha ukuthi iqembu lakhe le-QUIC nalo liyabandakanyeka ekusetshenzisweni kwenguqulo ephathelene ne-IEFT. "Senze imizamo emikhulu yokuguqula i-Google QUIC kule minyaka emihlanu edlule ukuhambisana nezinguquko ezenziwe yi-IETF, kanti inguqulo yakamuva yeGoogle QUIC inokufana okuningi ne-IETF QUIC," kufundeka lokhu okuthunyelwe ku-Google, Ngaphezu kwalokho, ucacisile ukuthi ezinye izinto bezingakatholakali.
Njengesibonelo, kuze kube manje abasebenzisi abaningi be-Chrome abakwazi ukuxhumana namaseva we-IETF QUIC ngaphandle kokunika amandla ezinye izinketho zomugqa womyalo. Ngokufanayo, IGoogle yengeze ukuthi manje ithole ukuthi i-IETF QUIC idlula kakhulu i-HTTP kuqhathaniswa ne-TLS 1.3 uma kuqhathaniswa ne-TCP.
Ngokuyinhloko, inkampani ithe i-latency ye-injini yokusesha ye-Google incishiswe ngaphezu kwe-2%. Isikhathi sokubhafa se-YouTube sehliswe ngaphezu kuka-9%. Ngokwengeziwe, ukusebenza kwamakhasimende kukhuphuke ngaphezu kuka-3% kumakhompyutha wedeskithophu.
Kumaselula, ukusebenza kwamakhasimende kukhuphuke ngaphezu kuka-7%. Lezi nezinye izizathu zisemuva kokushintshela kwe-Chrome enguqulweni ye-QUIC ye-IETF. “Siyajabula ukumemezela ukuthi i-Chrome isebenzisa ukwesekwa kwe-IETF QUIC (ikakhulukazi inguqulo ye-pilot engu-h3-29).
Namuhla, cishe abasebenzisi abangama-25% benguqulo ezinzile ye-Chrome basebenzisa i-h3-29, futhi sihlela ukukhulisa le nombolo emasontweni ezayo ngokuqhubeka nokuqapha idatha yokusebenza, ”kusho le nkampani eposini layo le-blog.
"I-Chrome izokweseka ngenkuthalo kokubili i-IETF QUIC h3-29 ne-Google QUIC (Q050) ukuvumela isikhathi samaseva asekela i-Q050 ukuthuthukela ku-IETF QUIC," engeza. I-Chrome m85 ayikasekeli i-IETF QUIC 0-RTT futhi iGoogle ilindele ukuthi lokhu kusebenza kube ngcono nakakhulu lapho ikhipha ukwesekwa kwe-IETF QUIC 0-RTT ezinyangeni ezizayo. Ngaphezu kwalokho, njengoba izinhlobo ze-IETF QUIC 30 no-31 zingenalo ushintsho olungaphula ukuhambisana, inkampani ayihlelile ukushintsha isihlonzi "over-the-wire".
Lokhu kusho ukuthi izoqhubeka nokulandela izinguquko kunguqulo ye-IETF, kepha izosebenza njengo-h3-29 / 0xff00001d.
Ngakho-ke, kuncoma ukuthi amaseva aqhubeke nokuxhasa i-h3-29 kuze kuphothulwe ama-RFC wokugcina uma efuna ukusebenzisana ne-Chrome. Kodwa-ke, uma i-IETF yenza ushintsho olwephula ukuhambisana kuphrojekthi yesikhathi esizayo, i-Chrome izosibuyisela emuva leso sinqumo.
Umthombo: https://blog.chromium.org