I-Paho Python client inendlela ye-proxy_set ebhaliwe. Lungiselela leyo client ngaphambi kokuxhumanisa ne-MQTT broker:

client.proxy_set(proxy_type=socks.SOCKS5,
                 proxy_addr='203.0.113.10',
                 proxy_port=1080)

Lokhu kucabanga ukuthi i-Paho client ehambisanayo kanye nokusekelwa kwe-SOCKS okudingekayo sekukhona. I-endpoint iyisibonelo kuphela. Kubroker efinyeleleka emphakathini emzileni we-proxy womphakathi ovunyelwe, uhlu lwama-proxy e-SOCKS5 lunikeza abangaba abangamagama okusingatha kanye nezingongoni; qinisekisa ukuthi i-node ivumela indawo yangempela ye-broker. Le ndlela ibhala izinhlobo ze-proxy ezisekelwayo futhi idlulisa i-proxying nge-PySocks.

I-broker isanegama layo lokusingatha, ingongo, izidingo ze-TLS kanye nokuqinisekiswa kwe-MQTT. I-akhawunti ye-proxy ayibi igama lomsebenzisi elithunyelwa kubroker. Ngokufanayo, ukusetha imininingwane ye-broker akukuqinisekisi ukugxuma kwe-proxy.

Hlola ukuthuthwa kwenguxa kanye nezindawo ezivunyelwe ze-proxy uma ukusethwa kwenguxa kwehluleka. I-proxy ethwala ukuphequlula iwebhu ayivumeli ngokuzenzakalela ingongo ye-TCP yebroker.

Gcina umjikelezo wenethiwekhi we-MQTT usebenza njengoba i-API ye-Paho idinga ngemva kokusethwa kwenguxa. Ukusungula umzila we-proxy kuyisinyathelo esisodwa; akushayeli ngokwako ama-keepalive, izingcingo zokubuyela kanye nokuqinisekisa kwe-MQTT.

Izihloko ezihlobene