Question

我看到2名护卫员在码头控制器从事同工行动。

第一:

public void GetNewsAsync()
{
    AsyncManager.OutstandingOperations.Increment();
    using (ManualResetEvent mre = new ManualResetEvent(false))
    {
        //Perform the actual operation in a worker thread
        ThreadPool.QueueUserWorkItem((object _mre) =>
        {
            //do some work in GetFeed that takes a long time
            var feed = GetFeed();

            AsyncManager.Parameters["Feed"] = feed;
            AsyncManager.OutstandingOperations.Decrement();
            mre.Set();

        }, mre);

        //Wait for the worker thread to finish
        mre.WaitOne(TimeSpan.FromSeconds(SomeNumberOfSecondsToWait));
    }
}

第二:

public void GetNewsAsync()
{
    AsyncManager.OutstandingOperations.Increment();

    //Perform the actual operation in a worker thread
    ThreadPool.QueueUserWorkItem((object x) =>
    {
        //do some work in GetFeed that takes a long time
        var feed = GetFeed();

        AsyncManager.Parameters["Feed"] = feed;
        AsyncManager.OutstandingOperations.Decrement();

    }, null);
}

A. 第一组 ToWait,第二部没有。两者都在工人的read子里进行工作,结果已转交GetNewsCom。

因此,我的问题是,处理Ajax呼吁GetNews、Wait或不等待的正确方式是什么?

Answer 1

我不知道你在什么地方看到了第一个例子,但那是完全打败了无声控制者宗旨的完全反主。同步行动的整个点是尽可能迅速地执行同步行动,释放主线。

This being said if GetFeed is a blocking call (which is what its name supposes it is) you get strictly 0 benefit from an asyncrhonous controller so the second example is also wrong for me. You could use a standard synchronous controller action in this case. With the second example you draw a thread from the pool and instead of blocking inside the main thread you block inside the other thread so the net effect is almost the same (in reality it s worse) if you had used a standard synchronous controller action.

因此,这两个例子将带来比任何好处更多的间接费用。

当你拥有一些I/O密集的亚特兰大时,如数据库或网络服务电话时,当你能够利用国际海事组织完成港口时,便宜使用同步控制器。 following article,为这一设想提供了良好范例。使用的<条码>新闻服务提供了真正的同步方法,在I/O网络电话中没有任何障碍。没有任何工人受到危害。

我也建议你读到。即便是用于传统的网络名称,它仍然包含一些非常有用的信息。

友情链接