.NET Core開發日誌——HttpClientFactory

當須要向某特定URL地址發送HTTP請求並獲得相應響應時，一般會用到HttpClient類。該類包含了衆多有用的方法，能夠知足絕大多數的需求。可是若是對其使用不當時，可能會出現意想不到的事情。

博客園官方團隊就趕上過這樣的問題，國外博主也記錄過相似的狀況，YOU'RE USING HTTPCLIENT WRONG AND IT IS DESTABILIZING YOUR SOFTWARE。

究其原因是一句看似正確的代碼引發的：

using(var client = new HttpClient())

對象所佔用資源應該確保及時被釋放掉，可是，對於網絡鏈接而言，這是錯誤的。

緣由有二，網絡鏈接是須要耗費必定時間的，頻繁開啓與關閉鏈接，性能會受影響；再者，開啓網絡鏈接時會佔用底層socket資源，但在HttpClient調用其自己的Dispose方法時，並不能馬上釋放該資源，這意味着你的程序可能會由於耗盡鏈接資源而產生預期以外的異常。

因此比較好的解決方法是延長HttpClient對象的使用壽命，好比對其建一個靜態的對象：

private static HttpClient Client = new HttpClient();

但從程序員的角度來看，這樣的代碼或許不夠優雅。

因此在.NET Core 2.1中引入了新的HttpClientFactory類。

它的用法很簡單，首先是對其進行IoC的註冊：

public void ConfigureServices(IServiceCollection services)
{
    services.AddHttpClient();
    services.AddMvc();
}

而後經過IHttpClientFactory建立一個HttpClient對象，以後的操做如舊，但不須要擔憂其內部資源的釋放：

public class MyController : Controller
{
    IHttpClientFactory _httpClientFactory;

    public MyController(IHttpClientFactory httpClientFactory)
    {
        _httpClientFactory = httpClientFactory;
    }

    public IActionResult Index()
    {
        var client = _httpClientFactory.CreateClient();
        var result = client.GetStringAsync("http://myurl/");
        return View();
    }
}

第一眼瞧去，可能不明白AddHttpClient方法與IHttpClientFactory有什麼關係，但查到其源碼後就能一目瞭然：

public static IServiceCollection AddHttpClient(this IServiceCollection services)
{
    if (services == null)
    {
        throw new ArgumentNullException(nameof(services));
    }

    services.AddLogging();
    services.AddOptions();

    //
    // Core abstractions
    //
    services.TryAddTransient<HttpMessageHandlerBuilder, DefaultHttpMessageHandlerBuilder>();
    services.TryAddSingleton<IHttpClientFactory, DefaultHttpClientFactory>();

    //
    // Typed Clients
    //
    services.TryAdd(ServiceDescriptor.Singleton(typeof(ITypedHttpClientFactory<>), typeof(DefaultTypedHttpClientFactory<>)));

    //
    // Misc infrastructure
    //
    services.TryAddEnumerable(ServiceDescriptor.Singleton<IHttpMessageHandlerBuilderFilter, LoggingHttpMessageHandlerBuilderFilter>());

    return services;
}

它的內部爲IHttpClientFactory接口綁定了DefaultHttpClientFactory類。

再看IHttpClientFactory接口中關鍵的CreateClient方法：

public HttpClient CreateClient(string name)
{
    if (name == null)
    {
        throw new ArgumentNullException(nameof(name));
    }

    var entry = _activeHandlers.GetOrAdd(name, _entryFactory).Value;
    var client = new HttpClient(entry.Handler, disposeHandler: false);

    StartHandlerEntryTimer(entry);

    var options = _optionsMonitor.Get(name);
    for (var i = 0; i < options.HttpClientActions.Count; i++)
    {
        options.HttpClientActions[i](client);
    }

    return client;
}

HttpClient的建立再也不是簡單的new HttpClient()，而是傳入了兩個參數：HttpMessageHandler handler與bool disposeHandler。disposeHandler參數爲false值時表示要重用內部的handler對象。handler參數則從上一句的代碼能夠看出是以name爲鍵值從一字典中取出，又由於DefaultHttpClientFactory類是經過TryAddSingleton方法註冊的，也就意味着其爲單例，那麼這個內部字典即是惟一的，每一個鍵值對應的ActiveHandlerTrackingEntry對象也是惟一，該對象內部中包含着handler。

下一句代碼StartHandlerEntryTimer(entry); 開啓了ActiveHandlerTrackingEntry對象的過時計時處理。默認過時時間是2分鐘。

internal void ExpiryTimer_Tick(object state)
{
    var active = (ActiveHandlerTrackingEntry)state;

    // The timer callback should be the only one removing from the active collection. If we can't find
    // our entry in the collection, then this is a bug.
    var removed = _activeHandlers.TryRemove(active.Name, out var found);
    Debug.Assert(removed, "Entry not found. We should always be able to remove the entry");
    Debug.Assert(object.ReferenceEquals(active, found.Value), "Different entry found. The entry should not have been replaced");

    // At this point the handler is no longer 'active' and will not be handed out to any new clients.
    // However we haven't dropped our strong reference to the handler, so we can't yet determine if
    // there are still any other outstanding references (we know there is at least one).
    //
    // We use a different state object to track expired handlers. This allows any other thread that acquired
    // the 'active' entry to use it without safety problems.
    var expired = new ExpiredHandlerTrackingEntry(active);
    _expiredHandlers.Enqueue(expired);

    Log.HandlerExpired(_logger, active.Name, active.Lifetime);

    StartCleanupTimer();
}

先是將ActiveHandlerTrackingEntry對象傳入新的ExpiredHandlerTrackingEntry對象。

public ExpiredHandlerTrackingEntry(ActiveHandlerTrackingEntry other)
{
    Name = other.Name;

    _livenessTracker = new WeakReference(other.Handler);
    InnerHandler = other.Handler.InnerHandler;
}

在其構造方法內部，handler對象經過弱引用方式關聯着，不會影響其被GC釋放。

而後新建的ExpiredHandlerTrackingEntry對象被放入專用的隊列。

最後開始清理工做，定時器的時間間隔設定爲每10秒一次。

internal void CleanupTimer_Tick(object state)
{
    // Stop any pending timers, we'll restart the timer if there's anything left to process after cleanup.
    //
    // With the scheme we're using it's possible we could end up with some redundant cleanup operations.
    // This is expected and fine.
    // 
    // An alternative would be to take a lock during the whole cleanup process. This isn't ideal because it
    // would result in threads executing ExpiryTimer_Tick as they would need to block on cleanup to figure out
    // whether we need to start the timer.
    StopCleanupTimer();

    try
    {
        if (!Monitor.TryEnter(_cleanupActiveLock))
        {
            // We don't want to run a concurrent cleanup cycle. This can happen if the cleanup cycle takes
            // a long time for some reason. Since we're running user code inside Dispose, it's definitely
            // possible.
            //
            // If we end up in that position, just make sure the timer gets started again. It should be cheap
            // to run a 'no-op' cleanup.
            StartCleanupTimer();
            return;
        }

        var initialCount = _expiredHandlers.Count;
        Log.CleanupCycleStart(_logger, initialCount);

        var stopwatch = ValueStopwatch.StartNew();

        var disposedCount = 0;
        for (var i = 0; i < initialCount; i++)
        {
            // Since we're the only one removing from _expired, TryDequeue must always succeed.
            _expiredHandlers.TryDequeue(out var entry);
            Debug.Assert(entry != null, "Entry was null, we should always get an entry back from TryDequeue");

            if (entry.CanDispose)
            {
                try
                {
                    entry.InnerHandler.Dispose();
                    disposedCount++;
                }
                catch (Exception ex)
                {
                    Log.CleanupItemFailed(_logger, entry.Name, ex);
                }
            }
            else
            {
                // If the entry is still live, put it back in the queue so we can process it 
                // during the next cleanup cycle.
                _expiredHandlers.Enqueue(entry);
            }
        }

        Log.CleanupCycleEnd(_logger, stopwatch.GetElapsedTime(), disposedCount, _expiredHandlers.Count);
    }
    finally
    {
        Monitor.Exit(_cleanupActiveLock);
    }

    // We didn't totally empty the cleanup queue, try again later.
    if (_expiredHandlers.Count > 0)
    {
        StartCleanupTimer();
    }
}

上述方法核心是判斷是否handler對象已經被GC，若是是的話，則釋放其內部資源，即網絡鏈接。

回到最初建立HttpClient的代碼，會發現並無傳入任何name參數值。這是得益於HttpClientFactoryExtensions類的擴展方法。

public static HttpClient CreateClient(this IHttpClientFactory factory)
{
    if (factory == null)
    {
        throw new ArgumentNullException(nameof(factory));
    }

    return factory.CreateClient(Options.DefaultName);
}

Options.DefaultName的值爲string.Empty。

DefaultHttpClientFactory缺乏無參數的構造方法，惟一的構造方法須要傳入多個參數，這也意味着構建它時須要依賴其它一些類，因此目前只適用於在ASP.NET程序中使用，還沒法應用到諸如控制檯一類的程序，但願以後官方可以對其繼續加強，使得應用範圍變得更廣。

public DefaultHttpClientFactory(
    IServiceProvider services,
    ILoggerFactory loggerFactory,
    IOptionsMonitor<HttpClientFactoryOptions> optionsMonitor,
    IEnumerable<IHttpMessageHandlerBuilderFilter> filters)