Azure Event Hubs a Python: AMQP ta WebSockets ta hanyar wakili na HTTP

Ga mai amfani da Event Hubs a Python da ke amfani da wakilin HTTP, saita ƙamus ɗin wakili na SDK da jigilar WebSocket yayin gina abokin ciniki:

from azure.eventhub import EventHubConsumerClient, TransportType

client = EventHubConsumerClient(
    fully_qualified_namespace=namespace,
    eventhub_name=eventhub_name,
    consumer_group='$Default',
    credential=credential,
    transport_type=TransportType.AmqpOverWebsocket,
    http_proxy={
        'proxy_hostname': 'proxy.example',
        'proxy_port': 8080,
    },
)

Filin suna, sunan Event Hub da takardar shaidar sune tsarin sabis ɗin da aikace-aikacen yake da shi. Ci gaba da kiran karɓar sa da tsarin rayuwar rufe abokin ciniki na yau da kullum.

Wannan ƙamus yana bayanin mai shiga tsakani kai tsaye. Ba shi ne taswirar tsarin makoma na http/https da Requests ke karɓa ba. Ga filin suna na Event Hubs na jama'a inda aka yarda da masu shiga tsakani na jama'a, jerin wakilan HTTP yana ba da ƴan takara don filayen sunan mai masauki da tasha ba tare da asusu ba. Ƙara maɓallan username da password idan ana buƙatar asusun wakilin da aka yi niyya.

AMQP ta WebSockets yana amfani da tashar 443 na sabis ɗin, yayin da jigilar AMQP ta yau da kullum ke amfani da 5671. Wakilin har yanzu yana buƙatar ba da izinin haɗin da ya samo zuwa filin suna na Event Hubs.

Takardar shaidar token na iya yin buƙatun HTTP daban yayin samun token. Saita jigilar da take goyan bayansa yadda ake buƙata lokacin da wannan hanyar tabbatarwa ita ma tana buƙatar wakilin.