01-08-2004, 07:49 AM
I'm writing a web app that keeps track of the health of some backend servers. However, I don't want the IIS machine to have to create traffic to the backend every time a user views the web page. For this I wanted to use a web service that would query the backend every 2 minutes and keep the data cached, then serve it out to IIS whenever it got a request. At the moment, however, each time IIS queries the web service the web service ends up querying the backend. I was under the impression that a web service was more like a daemon, where you could have two threads, one for answering requests and one for caching data. Is there a way to do this with a web service or is there a better alternative? Thanks!