Good points on IIS, it looks like a windows service is the way to go. I may write a web service to interact with the windows service, for good logical separation.
The assembly is a local spider/indexer type of program which runs slowly in the background. Thanks, Erick ----- Original Message ----- From: "Bryan Batchelder" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, May 29, 2002 11:33 AM Subject: Re: [DOTNET] Web service or windows service? I think you'd be better off with a windows service rather than web service.... I think with a web service you'll run into issues with IIS, such as timeouts, memory leaks, etc. What happens to an active web service when IIS recycles itself? I would guess that all child processes get recycled as well. Just curius - what is your assembly/service computing? --b Bryan Batchelder eBusiness Consultant ConnectWise, Inc. 813-935-7100 x 425 > -----Original Message----- > From: Erick Thompson [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, May 29, 2002 2:21 PM > To: [EMAIL PROTECTED] > Subject: [DOTNET] Web service or windows service? > > > 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. > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
