Dave, Take a look at the Asynchronous Invocation App
Dave, Take a look at the Asynchronous Invocation Application Block for .Net. (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag/html/PAIBlock.asp).� This was released from Microsoft's Patterns and Practices group a while back.� They have archived the block due to "lack of interest", but I've used it on a project with success.� Basically it provides a framework for you to have asynchronous sever work being completed on a backend server while still being able to publish some progress metrics for front end clients to monitor.� There are a few caveats, but most are not an issue and the block sounds�in line with�what you are wanting to accomplish.� I'd�say�you could�probably find other code blocks out there that will do the same, or you�could code your�own, but at least this block will give you�some ideas.� If you have any specific questions on the block then repost here, or shoot me an email. =================================== Date:��� Wed, 20 Apr 2005 17:13:32 -0400 From:��� Dave Heizer <[EMAIL PROTECTED]> Subject: 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
