>No, you don't understand ... I'm saying that you're *recommending* putting the code to access your WebService in a web page by publishing that method of doing it. It doesn't matter that someone wants to do it that way, it's not the best way to do it and you shouldn't recommend to do it that way. In your directions for how to use the WebService, just change your example to show how to do it the correct way, rather than from a WebPage. That's all ...

Even before all this thread, I did understand the concept entirely. Otherwise, I wouldn't have teach some topics on it.

Just to be clear, we had to respond to some user group needs. For them, they wanted to have it like that. We will however update the page to reflect the second approach, which is of more benefits, but is not necessary what some want. The reason is simple. Not everyone wants to maintain a separate engine for caching the data locally. Some would simply want to insert some code in their aspx page so they can query directly. But, those who wish to have it from a separate engine, will have the choice to do it and they will gain on performance and security as it'd be become from their own server.