Shafukan yanar gizo na Steam da zirga-zirgar wasa suna buƙatar hanyoyin cibiyar sadarwa daban-daban
Duba wane ɓangaren Steam ke gazawa da buƙatunsa na TCP ko UDP, maimakon ɗaukar ingantaccen proxy na burauza a matsayin goyon bayan kowace haɗin wasa.
Burauza na iya buɗe shagon Steam ta hanyar proxy na HTTP yayin da abokin ciniki na Steam ko wasa ba su iya haɗawa ba tukuna. Waɗannan ayyukan ba duka suna amfani da jigilar HTTP na burauza ba.
Valve ya lissafa buƙatun TCP da UDP don aiki da Steam, tare da ƙarin zirga-zirgar UDP don wasa, cibiyoyin sadarwar abokai, murya da Remote Play. Fara da takamaiman ɓangaren da ke gazawa: abun cikin yanar gizo, haɗin abokin ciniki, zaman wasa ko yawo na gida.
Proxy na HTTP CONNECT na yau da kullum yana ba da rami na TCP lokacin da manufofinsa suka yarda da tashar manufa. Tura SOCKS mai motsi na OpenSSH kuma yana ba da tura TCP. Babu ɗaya daga cikin waɗannan tsare-tsare da ke ba da zirga-zirgar UDP da wasa ke buƙata kai tsaye.
SOCKS5 yana bayyana UDP ASSOCIATE, amma amfani da shi yana buƙatar tallafi a cikin abokin ciniki mai turawa da uwar garken proxy duka. Samfurin da ke karɓar adireshin SOCKS5 don TCP ba ya aiwatar da relay na UDP saboda haka.
Duba buƙatun cibiyar sadarwa na wasan yanzu da hanyar da ƙungiyar ta yarda. Canza saitin jigila ɗaya a cikin abokin ciniki na Steam ba ya sake rubuta lambar cibiyar sadarwa ta kowace wasa da aka ƙaddamar daga gare shi. Valve kuma ya lura cewa ba za a iya sauya tashoshin da ake buƙata kai tsaye zuwa HTTP ko kowane kewayon al'ada ba.