I-Chrome iqalile ukunika amandla i-IETF QUIC kunye ne-HTTP/3

uphando ixelwe malunga nokuqala kokutshintsha eyakho inguqulelo yeprotocol QUIC Kumahluko aphuhliswe kwiinkcukacha ze-IETF. Uguqulelo lukaGoogle lweQUIC olusetyenziswa kwiChrome luyohluka kwiinkcukacha ezithile ukusuka kwinguqulelo Iinkcukacha ze-IETF. Kwangaxeshanye, iChrome ixhasa zombini iinketho zeprotocol, kodwa isasebenzisa ukhetho lwayo lwe-QUIC ngokungagqibekanga.

Ukuqala namhlanje, i-25% yabasebenzisi besebe elizinzile le-Chrome baye batshintshela ekusebenziseni i-IETF QUIC kwaye isabelo sabasebenzisi abanjalo siya kwandiswa kungekudala. Ngokwezibalo zeGoogle, xa kuthelekiswa ne-HTTP phezu kwe-TCP + TLS 1.3, i-IETF QUIC protocol ibonise ukunciphisa i-2% kwi-latency kwi-Google Search kunye nokunciphisa i-9% kwixesha lokubuyisela i-YouTube, ngokunyuka kwe-3% ye-desktop kunye ne-7. % yeenkqubo eziphathwayo

HTTP / 3 beka emgangathweni usebenzisa i-QUIC protocol njengothutho lwe-HTTP/2. Iprotocol ye-QUIC (i-Quick UDP Internet Connections) iye yaphuhliswa nguGoogle ukususela ngo-2013 njengenye indlela yokudibanisa i-TCP + TLS yeWebhu, ukuxazulula iingxaki ngokuseta ixesha elide kunye namaxesha othethathethwano loqhagamshelwano kwi-TCP kunye nokuphelisa ukulibaziseka xa iipakethi zilahlekile ngexesha ledatha. ugqithiselo. I-QUIC lulwandiso lweprotocol ye-UDP exhasa ukuphindaphindwa koqhagamshelo oluninzi kwaye ibonelele ngeendlela zofihlo ezilingana neTLS/SSL. Ngethuba lenkqubo yokulinganisa i-IETF, utshintsho lwenziwe kwiprotocol, eyakhokelela ekuveleni kwamasebe amabini ahambelanayo, enye ye-HTTP / 3, kunye neyesibini igcinwe yiGoogle.

umthombo: opennet.ru