I have a very long running process in a assembly that runs on a remote server. The process will run for about 2-3 weeks. All the management takes place via a set of web pages. There will also be a set of pages to monitor the process. The monitoring takes place in two different ways, first, the assembly raises events regularly (item processed, etc). In addition, the user can query the assembly (eg GetPercentFinished()) from a web page.
Given that everything is going to occur over the web, it made sense to make a web service that wrapped the dll that actually does the work. However, I'm not completely clear on how scope and web services interact. If a page makes an async call to a web service, is there any way for a later page to interact with that instance of the web service (to see the last item processed)? Or, should I create a standard windows service that drives the assembly, and have the web pages interact with that service? My feeling is a traditional windows service is the best solution here, but I haven't really worked with web services yet, so I thought I'd ask for a double check. Thanks, Erick You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
