Well this is really core to the .NET advantage so as I was saying previously everything is a web service in .NET. If it's an executable code, it can be a web service. So command line, daemon, service, whether it's a component, whether or not it's just a simple web application. So we don't have a prescriptive guide, we say if it's an executable, and you'd like to expose that as a web service then do so. Now obviously moving forward depending on where the framework you're taking advantage of web services, you may want to take advantage of web services ASP .NET, maybe inside of enterprise services, possibly as part of the core moding framework that we provide as well. So there is no concrete answer. If you want to expose those web services you can do it.