da Masu haɓaka Chrome sun sanar da cewa sun yi niyyar dakatar da tallafi inji Tura Server a cikin HTTP / 2 da ladabi na gQUIC, kazalika da rashin aiwatar da shi don yarjejeniyar HTTP / 3, wanda ke cikin matakin amincewa daidai. Ba a ba da fasahar Tura Saƙon ba a cikin yarjejeniyar HTTP / 1.1 daga farko.
Dalilin na kawar shine sha'awar rabu da babban matsala a cikin lambar, a cikin yanayin rashin buƙata kuma sharuɗɗan ka'idoji ne kawai don amfanin Sababbin Turawa na tushen Server.
Fasaha An ƙayyade Tura Server a cikin ƙa'idar HTTP / 2 da nufin inganta shigar da bayanai.
Baya ga masu bincike dangane da injin Chromium, ana aiwatar da goyan bayan Server Push a cikin Firefox da Safari, kuma a gefen uwar garke a nginx da Apache httpd.
Tare da Tura Turawa, uwar garken na iya aika albarkatu ga abokin ciniki ba tare da jiran bayyananniyar buƙatarku ba. An ɗauka cewa ta wannan hanyar uwar garke na iya hanzarta ɗora shafin, tunda fayilolin CSS, rubutun da hotunan da suka wajaba don bayar da shafin tuni za a sauya su zuwa gefensa lokacin da abokin ciniki ya buƙace shi.
Abokin ciniki ya haɗa kuma ya nemi takamaiman shafi, bayan haka uwar garken, ya danganta da tsarin sa ko abin da jigon rubutun da abokin ciniki ya aiko, ya fara tura wasu albarkatu ta hanyar tsarin HTTP / 2 da aka riga aka kafa, ba tare da jiran bukatar wadannan albarkatun ta bangaren abokin ciniki ba.
Abubuwan da aka sauya ta hanyar kiran turawa an adana su a gefen abokin ciniki a cikin keɓaɓɓiyar ɓoye da ke hade da haɗin HTTP / 2 na yanzu.
Lokacin, yayin aiwatar da shafi, abokin ciniki ya kai buƙatar albarkatun da ke tattare da shi (css, js, hotuna, da sauransu), ana yin cake cak kafin a aika kowane buƙata. Idan sabar ta riga ta canja wurin kuma tana cikin ɓoye, abokin ciniki ya sauke wannan albarkatun daga ɓoye na gida ba tare da yin buƙata ta waje zuwa sabar ba.
HTTP / 3 ƙa'idar yarjejeniya ce-RFC wacce kuma ke ma'anar tura uwar garke.
A halin yanzu Chrome yana tallafawa sarrafa turawar turawa akan HTTP / 2 da gQUIC, kuma wannan shine cire tallafi don ladabi duka. Chrome baya tallafawa turawa akan HTTP / 3 kuma ƙara tallafi baya kan taswirar hanya.
Kula da irin wannan ma'ajiyar yana wahalar da aiwatarwa Tura Server a bangaren abokin harka, amma hakan baya haifar da hanzarin daukar kaya idan aka kwatanta shi da bukatar samarda kayan aiki ta hanyar alamar "preload" kuma, a cewar wasu karatuttukan, har ma yana ƙara jinkiri.
A cewar kididdigar Google, Ba a rarraba fasahar Tura Tura ba. Misali, a cikin kwanaki 28 da suka gabata, 99,95% na haɗin HTTP / 2 bai yi amfani da Turawar Server ba. An lura da irin waɗannan alamun a yayin binciken a watan Yunin 2019, ma'ana, babu ci gaba a cikin turawar Server Push.
Har ila yau, a wannan shekara, 40% kawai daga saƙonnin da aka samu ta Server Push aka yi amfani da mai binciken, kuma shekaru biyu da suka gabata wannan adadi ya kasance 63,51% (saƙonnin da ba su dace ba, bai dace da shafin da aka sarrafa ba ko kuma sun riga sun kasance a cikin ɓoye) .
Madadin Server Turawa, don inganta kayan na shafin, da niyyar amfani da alama , dangane da abin da mai binciken zai iya neman kayan aiki ba tare da jiran amfani da shi a shafin ba.
A gefe guda, lodawa, idan aka kwatanta da Server Push, yana haifar da musayar fakiti mara buƙata (RTT), amma a ɗaya hannun, yana hana aika abubuwan da suka riga suka kasance a cikin maɓallin binciken.
Gabaɗaya, bambance-bambance na latency yayin amfani da Tura Turawa da preload ana ɗaukar su marasa kulawa. Toari da inganta kayan aiki, ana iya amfani da hanyar turawa ta Server don watsa bayanai daga sabar zuwa ga abokin ciniki, amma yarjejeniyar WebTransport (bisa QUIC) ta fi dacewa da wannan dalili, daidaitaccen abin da yake cikin ƙirar aiki .
Source:https://groups.google.com