Hi, There are a Pattern called "Service Activator" that could help to intiate the task in an asynchronous manner, but you must do a variation to the pattern giving to the client information about the state of your task.
I did this by two aproaches, the first was persisting the task state in the database, then the client after "activate" the service go to a poolling mode where ask to database for the state. My second aproach was the same but using queues. I hope this help Carlos Far�as -----Mensaje original----- De: Unmoderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] nombre de Dave Heizer Enviado el: Wednesday, April 20, 2005 5:14 PM Para: [email protected] Asunto: [ADVANCED-DOTNET] Long running processes I have a situation where our insurance application will have several long running processes to do things such as generate bills, calculation of values, and many other non-trivial tasks for 100,000's of policies. Some of these tasks may take hours to complete. Obviously we want these processes handle on our application server and not a client desktop, but the client does need to "submit" the process when they are ready and will need some progress / completion information returned. What approaches are most appropriate to handle such functions? =================================== This list is hosted by DevelopMentor� http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor� http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
