I have a process that I would like to run that needs to be controlled by a ASP.NET website. The problem is that the process is very data-intensive and can take 10-15 minutes. I'm pretty sure I will have to write a windows service to manage the long running process, and I will have to find some way to communicate between the two. The only requirements are listed below. Also, due to the complexity of the process and some resource availability issues, only one instance of the process can run at a time.
Requirements:
an end user (web site user) must be able to enqueue, edit the queue (reorder, or remove queued items), and cancel a long running process in the middle of execution using the website UI.the process provide status updates to the website ("Processing record 39 of 17,288")
The current implementation I am considering uses a common SQL table for queue manipulation, and having the website ...
Go to the complete details ...