如何在 Hangfire 中调用异步方法？
How to invoke async methods in Hangfire?
我有 asp.net 核心 API 应用程序，这是我第一次使用 HangFire。
在 .Net Core 应用程序中，我的所有方法都是异步的。基于 SO Post 在 hangfire 中调用异步方法时使用 wait() 不是个好主意。
同样根据 v1.6.0 中的 hangfire support issue，添加了异步支持。我正在使用 1.6.12 版，但我仍然没有看到异步支持。
如何从 Enqueue 调用异步方法。目前我正在使用 wait()
public class MyController : Controller
{
private readonly Downloader _downlaoder;
private readonly IBackgroundJobClient _backgroungJobClient;
public MyController(Downloader downloader, IBackgroundJobClient backgroungJobClient)
{
_downlaoder = downloader;
_backgroungJobClient = backgroungJobClient;
}
[HttpPost]
public void Post([FromBody]IEnumerable<string> files)
{
_backgroungJobClient.Enqueue(() => _downloader.DownloadAsync(files).Wait());
}
}
中的示例之一
只需删除 Wait 阻塞调用
_backgroungJobClient.Enqueue(() => _downloader.DownloadAsync(files));
该方法现在知道如何处理 returns Task
的 Func
The enqueueing logic is the same for sync and async methods. In early
betas there was a warning CS4014, but now you can remove all the
#pragma warning disable statements. It was implemented by using Expression<Func<Task>> parameter overloads.
BackgroundJob.Enqueue(() => HighlightAsync(snippet.Id));
注：
That’s not a real asynchrony
Please consider this feature as a syntactic sugar. Background
processing hasn’t became asynchronous. Internally it was implemented
using the Task.Wait method, so workers don’t perform any processing,
while waiting for a task completion. Real asynchrony may come in
Hangfire 2.0 only, and it requires a lot of breaking changes to the
existing types.
我有 asp.net 核心 API 应用程序，这是我第一次使用 HangFire。
在 .Net Core 应用程序中，我的所有方法都是异步的。基于 SO Post 在 hangfire 中调用异步方法时使用 wait() 不是个好主意。
同样根据 v1.6.0 中的 hangfire support issue，添加了异步支持。我正在使用 1.6.12 版，但我仍然没有看到异步支持。
如何从 Enqueue 调用异步方法。目前我正在使用 wait()
public class MyController : Controller
{
private readonly Downloader _downlaoder;
private readonly IBackgroundJobClient _backgroungJobClient;
public MyController(Downloader downloader, IBackgroundJobClient backgroungJobClient)
{
_downlaoder = downloader;
_backgroungJobClient = backgroungJobClient;
}
[HttpPost]
public void Post([FromBody]IEnumerable<string> files)
{
_backgroungJobClient.Enqueue(() => _downloader.DownloadAsync(files).Wait());
}
}
只需删除 Wait 阻塞调用
_backgroungJobClient.Enqueue(() => _downloader.DownloadAsync(files));
该方法现在知道如何处理 returns Task
的 FuncThe enqueueing logic is the same for sync and async methods. In early betas there was a warning CS4014, but now you can remove all the
#pragmawarning disable statements. It was implemented by usingExpression<Func<Task>>parameter overloads.BackgroundJob.Enqueue(() => HighlightAsync(snippet.Id));
注：
That’s not a real asynchrony
Please consider this feature as a syntactic sugar. Background processing hasn’t became asynchronous. Internally it was implemented using the Task.Wait method, so workers don’t perform any processing, while waiting for a task completion. Real asynchrony may come in Hangfire 2.0 only, and it requires a lot of breaking changes to the existing types.