Azure Notification Hubs .NET: wane saitin wakili ne zai yi nasara?

Sanya NotificationHubSettings.Proxy ko hanyar HTTP da aka bayar, tare da lura da fifikon HttpClient da MessageHandler na constructor.

A cikin Notification Hubs .NET API da NotificationHubSettings, ana iya bayar da wakili yayin gina abokin ciniki:

var settings = new Microsoft.Azure.NotificationHubs.NotificationHubSettings
{
    Proxy = new System.Net.WebProxy("http://proxy.example:8080")
};
var hub = new Microsoft.Azure.NotificationHubs.NotificationHubClient(
    hubConnectionString, hubName, settings);

Igiyar haɗi da sunan hub sun kasance saitin sabis ɗin. Ƙarshen HTTP na jama'a daga jerin wakilan HTTP zai iya cika adireshin WebProxy a hanyar gini ta asali.

Akwai ka'idar tsari a cikin wannan constructor:

  1. Ana fara amfani da HttpClient da aka bayar.
  2. In ba haka ba, MessageHandler da aka bayar yana ƙirƙirar abokin ciniki na HTTP.
  3. In ba haka ba, Proxy yana ƙirƙirar HttpClientHandler da aka saita don wakili.
  4. Idan ba a bayar da kome ba, constructor yana ƙirƙirar abokin ciniki na HTTP na asali.

Idan aikace-aikacen ya riga ya bayar da HttpClient ko MessageHandler, saita wakilin wannan hanyar maimakon tsammanin fasalin Proxy daban zai rinjaye shi.

Don asusun wakili, saita takardun shaida akan WebProxy kafin gini. Suna tabbatarwa ga mai shiga tsakani, ba ga Notification Hub ba.

Tsofaffin misalai suna ambaton NotificationHubClientSettings. Daidaita nau'in saiti da constructor da fakitin da aka shigar ya bayyana, maimakon haɗa wannan sunan cikin API da ke tsammanin NotificationHubSettings.

Labarai masu alaƙa