blocks|key|395778|text|如果您正在构建一个类库，那么您的库的用户可能希望异步使用您的库。我认为这就是最大的原因。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|395779|你也不知道你的库将如何被使用。也许用户将处理大量的请求，异步处理将有助于它更快、更高效地执行。|395780|如果您可以简单地做到这一点，请尽量不要将负担放在您的库的用户身上，当您可以为他们处理它时，他们会尝试使流程异步。|395781|我不会使用异步版本的唯一原因是，如果我试图支持一个还没有内置异步支持的旧版本的.NET。|395782|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

If you're building a class library, then perhaps the users of your library would like to use your library asynchronously. I think that's the biggest reason right there.

You also don't know how your library is going to be used. Perhaps the users will be processing lots and lots of requests, and doing so asynchronously will help it perform faster and more efficient.

If you can do so simply, try not to put the burden on the users of your library trying to make the flow asynchronous when you can take care of it for them.

The only reason I wouldn't use the async version is if I were trying to support an older version of .NET that does not already have built in async support.

blocks|key|395836|text|在我的例子中，被接受的答案不起作用。我从一个没有异步操作的MVC应用程序调用API。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|395837|这就是我是如何让它工作的：|395838|private+static+readonly+TaskFactory+_myTaskFactory+=+new+TaskFactory(CancellationToken.None,+TaskCreationOptions.None,+TaskContinuationOptions.None,+TaskScheduler.Default);
public+static+T+RunSync<T>(Func<Task<T>>+func)
++++{+++++++++++
++++++++CultureInfo+cultureUi+=+CultureInfo.CurrentUICulture;
++++++++CultureInfo+culture+=+CultureInfo.CurrentCulture;
++++++++return+_myTaskFactory.StartNew<Task<T>>(delegate
++++++++{
++++++++++++Thread.CurrentThread.CurrentCulture+=+culture;
++++++++++++Thread.CurrentThread.CurrentUICulture+=+cultureUi;
++++++++++++return+func();
++++++++}).Unwrap<T>().GetAwaiter().GetResult();
++++}|code-block|syntax|javascript|395839|然后我这样叫它：|395840|Helper.RunSync(new+Func<Task<ReturnTypeGoesHere>>(async+()+=>+await+AsyncCallGoesHere(myparameter)));|395841|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

In my case the accepted answer did not work. I was calling the API from an MVC application which had no async actions.

This is how I managed to make it work:

<pre><code>private static readonly TaskFactory _myTaskFactory = new TaskFactory(CancellationToken.None, TaskCreationOptions.None, TaskContinuationOptions.None, TaskScheduler.Default);
public static T RunSync&lt;T&gt;(Func&lt;Task&lt;T&gt;&gt; func)
 { 
 CultureInfo cultureUi = CultureInfo.CurrentUICulture;
 CultureInfo culture = CultureInfo.CurrentCulture;
 return _myTaskFactory.StartNew&lt;Task&lt;T&gt;&gt;(delegate
 {
 Thread.CurrentThread.CurrentCulture = culture;
 Thread.CurrentThread.CurrentUICulture = cultureUi;
 return func();
 }).Unwrap&lt;T&gt;().GetAwaiter().GetResult();
 }
</code></pre>

Then I called it like this:

<pre><code>Helper.RunSync(new Func&lt;Task&lt;ReturnTypeGoesHere&gt;&gt;(async () =&gt; await AsyncCallGoesHere(myparameter)));
</code></pre>

blocks|key|395891|text|public+static+class+AsyncHelper++
{
++++private+static+readonly+TaskFactory+_taskFactory+=+new
++++++++TaskFactory(CancellationToken.None,
++++++++++++++++++++TaskCreationOptions.None,
++++++++++++++++++++TaskContinuationOptions.None,
++++++++++++++++++++TaskScheduler.Default);

++++public+static+TResult+RunSync<TResult>(Func<Task<TResult>>+func)
++++++++=>+_taskFactory
++++++++++++.StartNew(func)
++++++++++++.Unwrap()
++++++++++++.GetAwaiter()
++++++++++++.GetResult();

++++public+static+void+RunSync(Func<Task>+func)
++++++++=>+_taskFactory
++++++++++++.StartNew(func)
++++++++++++.Unwrap()
++++++++++++.GetAwaiter()
++++++++++++.GetResult();
}|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|395892|然后|unstyled|395893|AsyncHelper.RunSync(()+=>+DoAsyncStuff());|395894|如果使用类将异步方法作为参数传递，则可以以安全方式从同步方法调用异步方法。|395895|这里有解释：https://cpratt.co/async-tips-tricks/|offset|length|395896|entityMap|0|LINK|mutability|MUTABLE|url|https://cpratt.co/async-tips-tricks/^0|0|0|0|0|6|10|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|X|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|Y|8|@]|9|@]|A|$B|C]]|$1|I|3|J|5|F|7|Z|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|10|8|@]|9|@$M|11|N|12|1|13]]|A|$]]|$1|O|3|-4|5|F|7|14|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

<pre><code>public static class AsyncHelper 
{
 private static readonly TaskFactory _taskFactory = new
 TaskFactory(CancellationToken.None,
 TaskCreationOptions.None,
 TaskContinuationOptions.None,
 TaskScheduler.Default);

 public static TResult RunSync&lt;TResult&gt;(Func&lt;Task&lt;TResult&gt;&gt; func)
 =&gt; _taskFactory
 .StartNew(func)
 .Unwrap()
 .GetAwaiter()
 .GetResult();

 public static void RunSync(Func&lt;Task&gt; func)
 =&gt; _taskFactory
 .StartNew(func)
 .Unwrap()
 .GetAwaiter()
 .GetResult();
}
</code></pre>

Then

<pre><code>AsyncHelper.RunSync(() =&gt; DoAsyncStuff());
</code></pre>

if you use that class pass your async method as parameter you can call the async methods from sync methods in a safe way.

it's explained here :
<a href="https://cpratt.co/async-tips-tricks/" rel="noreferrer">https://cpratt.co/async-tips-tricks/</a>

blocks|key|178005|text|对于现在遇到这个问题的任何人，.NET+5.0已经在HttpClient中添加了一个同步Send方法。https://github.com/dotnet/runtime/pull/34948|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|178006|优点以及为什么在这里详细讨论-+https://github.com/dotnet/runtime/issues/32125|178007|因此，您可以使用它而不是SendAsync。例如|178008|public+string+GetValue()
{
++++var+client+=+new+HttpClient();
++++++++++++
++++var+webRequest+=+new+HttpRequestMessage(HttpMethod.Post,+"http://your-api.com")
++++{
++++++++Content+=+new+StringContent("{+'some':+'value'+}",+Encoding.UTF8,+"application/json")
++++};

++++var+response+=+client.Send(webRequest);

++++using+var+reader+=+new+StreamReader(response.Content.ReadAsStream());
++++++++++++
++++return+reader.ReadToEnd();
}|code-block|syntax|javascript|178009|这段代码只是一个简化的例子，它还没有准备好投入生产。|178010|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/dotnet/runtime/pull/34948|1|https://github.com/dotnet/runtime/issues/32125^0|Q|A|18|4|1F|18|0|0|G|1A|1|0|C|9|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@$9|15|A|16|1|17]]|E|$]]|$1|F|3|G|5|6|7|18|8|@]|D|@$9|19|A|1A|1|1B]]|E|$]]|$1|H|3|I|5|6|7|1C|8|@$9|1D|A|1E|B|C]]|D|@]|E|$]]|$1|J|3|K|5|L|7|1F|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|1G|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|1H|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|X]]|Y|$5|T|U|V|E|$W|Z]]]]

For anyone coming across this now, .NET 5.0 has added a synchronous <code>Send</code> method to <code>HttpClient</code>. <a href="https://github.com/dotnet/runtime/pull/34948" rel="noreferrer">https://github.com/dotnet/runtime/pull/34948</a>
The merits as too why where discussed at length here - <a href="https://github.com/dotnet/runtime/issues/32125" rel="noreferrer">https://github.com/dotnet/runtime/issues/32125</a>
You can therefore use this instead of <code>SendAsync</code>. For example
<pre><code>public string GetValue()
{
 var client = new HttpClient();
 
 var webRequest = new HttpRequestMessage(HttpMethod.Post, &quot;http://your-api.com&quot;)
 {
 Content = new StringContent(&quot;{ 'some': 'value' }&quot;, Encoding.UTF8, &quot;application/json&quot;)
 };

 var response = client.Send(webRequest);

 using var reader = new StreamReader(response.Content.ReadAsStream());
 
 return reader.ReadToEnd();
}
</code></pre>
This code is just a simplified example, it's not production ready.

I am building a class library to interact with an API. I need to call the API and process the XML response. I can see the benefits of using <code>HttpClient</code> for Asynchronous connectivity, but what I am doing is purely synchronous, so I cannot see any significant benefit over using <code>HttpWebRequest</code>.

If anyone can shed any light I would greatly appreciate it. I am not one for using new technology for the sake of it.

Why use HttpClient for Synchronous Connection

我正在构建一个类库来与API交互。我需要调用API并处理XML响应。我可以看到使用HttpClient进行异步连接的好处，但是我所做的是纯同步的，所以我看不到使用HttpWebRequest有什么显著的好处。如果有人能提供任何线索，我将不胜感激。我不是一个为了使用新技术而使用它的人。

问为什么要使用HttpClient进行同步连接
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为什么要使用HttpClient进行同步连接EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为什么要使用HttpClient进行同步连接
EN