Google ya yi gargadin cewa goyon bayan fasahar Push Server za a kashe a cikin sakin Chrome 106, wanda aka shirya a ranar 27 ga Satumba. Canje-canjen kuma za su shafi sauran masu bincike bisa tushen lambar Chromium. An ayyana fasahar Push ta uwar garke a cikin ka'idodin HTTP/2 da HTTP/3, kuma tana ba uwar garken damar aika albarkatu zuwa abokin ciniki ba tare da jiran buƙatun su ba. Ana tsammanin cewa ta wannan hanyar uwar garken zata iya hanzarta loda shafi, tunda fayilolin CSS, rubutun da kuma hotunan da ake buƙata don fassara shafin an riga an canza su zuwa gefensa a lokacin da abokin ciniki ya buƙace shi.
Dalilin da aka ambata don dakatar da tallafi shine rikitarwa maras buƙata na aiwatar da fasaha lokacin da mafi sauƙi kuma daidaitattun hanyoyin da za a samu, kamar tag , a kan abin da mai bincike zai iya neman albarkatun ba tare da jira don amfani da shi a shafin ba. A gefe guda, preload, idan aka kwatanta da Server Push, yana haifar da musayar fakitin da ba dole ba (RTT), amma a daya bangaren, yana guje wa aika albarkatun da ke cikin cache na burauzar. Gabaɗaya, bambance-bambance a cikin latency lokacin amfani da Push Server da preload ana lura dasu azaman marasa mahimmanci.
Don fara pre-loading a gefen uwar garken, an ba da shawarar yin amfani da lambar amsa HTTP 103, wanda ke ba ku damar sanar da abokin ciniki game da abubuwan da ke cikin wasu shugabannin HTTP nan da nan bayan buƙatar, ba tare da jiran uwar garken don kammala duk ayyukan da suka shafi. buƙatun kuma fara hidimar abun ciki. Hakazalika, zaku iya ba da alamu game da abubuwan da ke da alaƙa da shafin da ake ba da sabis waɗanda ƙila a riga an loda su (misali, kuna iya samar da hanyoyin haɗi zuwa CSS da JavaScript da aka yi amfani da su akan shafin). Bayan samun bayanai game da irin waɗannan albarkatu, mai binciken zai iya fara zazzage su ba tare da jiran babban shafin ya gama yin aiki ba, wanda ke rage lokacin sarrafa buƙatun gabaɗaya.
Baya ga inganta lodin albarkatu, Hakanan ana iya amfani da injin Push na uwar garken don jera bayanai daga uwar garken zuwa abokin ciniki, amma saboda waɗannan dalilai ƙungiyar W3C tana haɓaka ƙa'idar WebTransport. An tsara tashar sadarwa a cikin WebTransport a saman HTTP/3 ta amfani da ka'idar QUIC azaman sufuri. WebTransport yana ba da irin waɗannan fasalulluka na ci gaba kamar shirya watsawa cikin rafuka da yawa, rafukan da ba a kai ba, bayarwa ba tare da la'akari da tsarin da aka aika fakiti (ba tare da oda ba), amintattun hanyoyin isarwa mara inganci.
Bisa kididdigar Google, ba a amfani da fasahar Push ta Server. Ko da yake an haɗa Push Server a cikin ƙayyadaddun HTTP/3, a aikace yawancin uwar garken da samfuran software na abokin ciniki, gami da mai binciken Chrome, ba sa aiwatar da shi ta asali. A cikin 2021, kusan kashi 1.25% na rukunin yanar gizon da ke gudanar da HTTP/2 sun yi amfani da Push Server. A bana wannan adadi ya ragu zuwa 0.7%.
source: budenet.ru