UGoogle uxeliwe kwiintsuku ezimbalwa ezidlulileyo sele iqalile Ukuhanjiswa kwe-HTTP / 3 kunye ne-IETF QUIC kwiChannel nakwisibhengezo, uthi ulindele ukuba olu hlaziyo luzise ukuphuculwa kokusebenza, ngakumbi ngenkxaso ye-QUIC.
I-QUIC yinkqubo entsha yothutho yenethiwekhi edibanisa amanqaku e-TCP, TLS kunye nokunye. I-HTTP / 3 yinguqulelo yamva nje ye-HTTP, umthetho ophethe uninzi lwezithuthi zewebhu. I-HTTP / 3 isebenza kuphela kwi-QUIC.
Umkhosi woBunjineli be-Intanethi, okanye i-IETF, wazisa i-HTTP / 2 ngo-2015 kwaye olunye lophuculo olukhulu olwenziwe yinkxaso yokuphindaphindwa.
Nangona kunjalo, yayisebenzisa i-TCP njengeprotocol yezothutho kunye neendlela zokulahleka kwakhona kwi-TCP, ke iipakethi ezilahlekileyo zisenokubangela ukulibaziseka kuyo yonke imicimbi esebenzayo.
Ngokwamkela i-QUIC, i-HTTP / 3 inokuqhubeka nokuphucula inkqubo yokuhambisaKuba iipakethi ezilahlekileyo kule meko zichaphazela kuphela imicimbi echaphazelekayo.
Enyanisweni, I-QUIC yaveliswa nguGoogle ekuqaleni Kwaye okokuqala kwabhengezwa ngo-2013. Ukusukela ngoko, umthetho wobudala sele uneminyaka yobudala kwaye okwangoku uxanduva lokuthwala isithathu sezithuthi zikaGoogle.
Ke ngo-2015, uphuhliso lwe-QUIC lwadlulela ezandleni ze-IETF, imigangatho yemigangatho ejongene nokugcina iinkqubo ze-Intanethi. IETF iphucule i-QUIC ngotshintsho oluninzi. Ukuza kuthi ga ngoku, zimbini iinkqubo ezifanayo kodwa ezahlukileyo, ezi: I-Google QUIC kunye ne-IETF QUIC.
UGoogle ubhengeze ukuba ihlala isebenzisa uhlobo lwayo lwe-QUIC, Kodwa iqela lakhe le-QUIC liyabandakanyeka ekuphunyezweni kwenguqu ye-IEFT. "Senze iinzame ezibonakalayo zokuguqula i-Google QUIC kule minyaka mihlanu idlulileyo ukuze sihambisane notshintsho olwenziwe yi-IETF, kunye nenguqulelo yamva nje yeGoogle QUIC inezinto ezininzi ezifanayo kwi-IETF QUIC," iposti yebhlog. isuka kuGoogle, ukongeza, icacisile ukuba ezinye izinto bezingekabikho.
Njengomzekelo, ukuza kuthi ga ngoku uninzi lwabasebenzisi beChannel abakwazi ukunxibelelana neeseva ze-IETF QUIC ngaphandle kokwenza ezinye iinketho zomgca wokuyalela. Ngokufanayo, UGoogle wongeze ukuba ngoku ifumanise ukuba i-IETF QUIC iyenza ngakumbi i-HTTP xa kuthelekiswa ne-TLS 1.3 xa kuthelekiswa ne-TCP.
Ngokukodwa, inkampani yathi i-injini yokukhangela yeGoogle iyancitshiswa ngaphezulu kwe-2%. Ixesha lokugcina ixesha likaYouTube lincitshisiwe ngaphezulu kwe-9%. Ukongeza, ukusebenza kwabaxhasi kuye kwanda ngaphezulu kwe-3% kwiikhompyuter zedesktop.
Kwiifowuni eziphathwayo, ukusebenza kwabathengi kunyuke ngaphezulu kwe-7%. Ezi kunye nezinye izizathu zisemva kotshintsho lweChannel kuhlobo lwe-QUIC ye-IETF. “Siyavuya ukwazisa ukuba iChannel iphumeza inkxaso ye-IETF QUIC (ngakumbi inguqulelo ye-pilot engu-h3-29).
Namhlanje, malunga neepesenti ezingama-25 zabasebenzisi bohlobo oluzinzileyo lwe-Chrome basebenzisa i-h3-29, kwaye siceba ukwandisa eli nani kwiiveki ezizayo ngokuqhubeka nokujonga idatha yokusebenza, "utshilo inkampani kwiposti yayo .
"I-Chrome izakuxhasa ngokubonakalayo zombini i-IETF QUIC h3-29 kunye nohlobo lweGoogle QUIC (Q050) ukuvumela ixesha leeseva ezixhasa i-Q050 ukunyusela kwi-IETF QUIC," wongeze watsho. I-Chrome m85 ayikaxhasi i-IETF QUIC 0-RTT kwaye uGoogle ulindele ukuba le ntsebenzo ibe ngcono nangakumbi xa ikhupha inkxaso ye-IETF QUIC 0-RTT kwiinyanga ezizayo. Ngapha koko, kuba iinguqulelo ze-IETF ze-QUIC 30 kunye ne-31 zingenalo utshintsho olunokwaphula ukuhambelana, inkampani ayicwangcisi ukutshintsha isazisi "ngaphezulu kwe-ucingo".
Oku kuthetha ukuba iya kuqhubeka nokulandela utshintsho kuhlobo lwe-IETF, kodwa i iya kuphumeza njenge-h3-29 / 0xff00001d.
Ke ngoko, icebisa ukuba iiseva ziqhubeke nokuxhasa i-h3-29 kude kube kugqityiwe ii-RFCs zokugqibela ukuba bafuna ukusebenzisana neChannel. Nangona kunjalo, ukuba i-IETF yenza utshintsho olwaphula ukuhambelana kwiprojekthi yexesha elizayo, iChannel isijike eso sigqibo.
Umthombo: https://blog.chromium.org