Strategy for managing long processes in a web application?

Question

I am developing an asp.net web application. A feature of the application is that the user can queue up several lengthy operations, and then click start the queue will be processed.

I do not want the user to sit and wait for the completion of all operations or to really leave the browser / application open. However, if they stay or return to the page, I would like them to be able to see the status of each work, i.e. Waiting completed or failed.

Naturally, I am looking for the most reliable, reliable and scalable solution, since a huge number of jobs in the queue is potentially possible at any time.

From my research, it was suggested that asp.net could call the Windows service? Perhaps this is hosting a WCF web service.

Look for any advice from those who may have had a similar requirement in the past.

Answer 1

Also check out MSMQ,

http://msdn.microsoft.com/en-us/library/ms711472(v=vs.85).aspx

Basically, a web application puts a "task" or "group of tasks" in a queue.

The service works constantly, causing the next "work" or "group of tasks" and getting to work with them.

( - ), - .

Enjoy.

Answer 2

, Windows, . , Quartz.NET, . , Windows . - , , . , - ( , , , ..).

- , Windows, , - ASP.NET, . ASP.NET , .

Answer 3

Windows - . , .
, Fire And Forget. ( ) . , :
http://msdn.microsoft.com/en-us/magazine/cc163587.aspx
http://msdn.microsoft.com/en-us/magazine/cc164128.aspx#S6
http://msdn.microsoft.com/en-us/library/ff647332.aspx

Answer 4

. -, . , , . , , . .

1) , id .
2) - , .
3) , , db. .
4) , ajax x .

.