策略在Web应用程序管理长时间运行的进程？ [英] Strategy for managing long running processes in a web app?

问题描述

我开发一个web asp.net应用程序。该应用程序的一个特点是，用户能够排队了一批长期运行的操作，然后点击运行队列将被处理。

I am developing a web asp.net application. A feature of the application is that the user is able to queue up a number of long running operations, then hit run the queue will be processed.

我不希望用户不得不坐下来，等待所有操作完成或确实保持浏览器/应用程序打开。但是他们应该留在或重返我希望他们能够看到每个作业即等待状态的页面，进行中，已完成或失败。

I don't want the user to have to sit and wait for all the operations to  complete or indeed keep the browser / application open. However should they remain or return to the page I would like them to be able to see the status of each job i.e. Waiting, in progress, completed or failed.

我自然寻找最强大，可靠和可扩展的解决方案，为可能有可能在任何时候大量的队列中的作业。

I am naturally looking for the most robust, reliable and scalable solution as potentially there maybe a great number of jobs in the queue at any time.

从我的研究已经表明，在asp.net可以打电话到窗口服务？也许是承载WCF web服务。

From my research it has been suggested that the asp.net could call into windows service? That perhaps is hosting a WCF web service.

寻找任何人的意见谁可能已经在过去类似的规定。

Looking for any advice from anyone who might have had a similar requirement in the past.

推荐答案

还检查了MSMQ，

<一个href=\"http://msdn.microsoft.com/en-us/library/ms711472(v=vs.85).aspx\">http://msdn.microsoft.com/en-us/library/ms711472(v=vs.85).aspx

基本上Web应用程序会将的工作组，工作或进入队列中。

Basically the web application places the "job" or "group of jobs" into a queue.

该服务持续运行，出队的下一个工作或作业组和获得正事他们。

The service runs constantly, dequeueing the next "job" or "group of jobs" and getting down to business with them.

在完成后，服务将结果放到另一个队列或一个数据库（或其他共享资源）的Web应用程序访问和显示的状态或结果。

When completed, the service puts the results into another queue or in a DB (or some other shared resource) that the web application accesses and displays the status of, or the results of.

享受。

这篇关于策略在Web应用程序管理长时间运行的进程？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！