A cikin manhajar da ke amfani da Azure IoT Python SDK tuni, zaɓi hanyar jigilar MQTT da zaɓuɓɓukan wakilinta tare. Wannan saitin yana zaɓar MQTT a kan WebSockets:

proxy = ProxyOptions(proxy_type='HTTP',
                     proxy_addr='203.0.113.10', proxy_port=8080)
client = IoTHubDeviceClient.create_from_connection_string(
    connection_string, websockets=True, proxy_options=proxy
)

Azuzuwan sun fito ne daga bayanan da aka rubuta na SDK. Bayar da igiyar haɗin na'urar ta hanyar saitin sirri na manhajar kuma maye gurbin misalin ƙarshen wakili. Don ƙarshen IoT Hub da ake iya isa ga jama'a inda aka yarda da masu shiga tsakani na jama'a, jerin wakilan HTTP yana ba da 'yan takara don masaukin da tashar HTTP; tabbatar cewa sabis ɗin ya yarda da hanyar zuwa inda aka nufa. Waɗannan zaɓuɓɓuka ne bayyanannu na SDK; wakilin da ke aiki a burauza ko saitin gama gari na tsarin aiki ba ya kafa hanyar abokin cinikin na'urar.

Duba bayanin ProxyOptions don nau'in wakilin da aka zaɓa. Yana bambanta filayen HTTP, SOCKS4 da SOCKS5 kuma yana rubuta halin sunan mai amfani/ kalmar sirri na musamman ga kowane nau'i, gami da iyakoki na HTTP. Kasancewar fili ba ya ba da tabbacin kowace hanyar tantancewa.

Asusun wakili da asalin na'urar suna ba da izini ga matakai daban-daban. Musanya mai shiga tsakani da aka ƙi zai iya dakatar da haɗin kafin dillali ya tantance shaidar na'urar. Zaɓin WebSockets kuma yana barin ƙuntatawar wakilin kan inda aka nufa da shiga suna aiki.

Yi rikodin hanyar da aka zaɓa, inda aka nufa da matakin farko da ya kasa. Abokin cinikin SDK, aiwatar da wakili da hanyar da aka yarda dole su yarda da juna; ko buƙatar burauza mai nasara ko ikirarin gama gari cewa SOCKS yana ɗaukar kowane yarjejeniya ba ya samar da wannan jituwa.

Labarai masu alaƙa