asked on

Long Running Tasks in ASP.NET 2.0

I search asp.net 2.0 web service long running task in google, and get back some results about how to run a long running task in the ASP.NET 2.0 (Visual Studio 2005).

http://aspalliance.com/329_Start_a_Long_Process_from_a_Web_Page_Using_XML_Web_Services

http://books.google.com.hk/books?id=Z_QetkvQYScC&pg=PA1183&lpg=PA1183&dq=asp.net+2.0+web+service+long+running+task&source=bl&ots=X4_HIGN7Z-&sig=H3uP5BSlF3jZVxPNdWSohHAd6Gg&hl=zh-TW&sa=X&ei=kaUJT6myO8iwiQeo9PSTCQ&ved=0CGIQ6AEwBjgU#v=onepage&q=asp.net%202.0%20web%20service%20long%20running%20task&f=false

Because our users can close the browser during processing and check the status in the other page later, is there any recommendation other than using [SoapDocumentMethod(OneWay=true)] web method?

Easwaran Paramasivam

You can create a windows service and run the long running process during less business hours.

The service program may use threads efficiently.

Please do google those topics and try to implement in your application.

kaufmed

The web was designed to be stateless. Once a request has been satisfied, that's it--there is nothing to check later. You need to add something that will maintain the state for your process. Have you considered having a database that your long-running task can update with its current status? You ASP.NET page can query this database to check the status at later times.

ASKER CERTIFIED SOLUTION