Hey all, I've done a fair bit of Silverlight and WPF over the last few years and so my experience with web services and their usage is from that perspective. Usually, when you think of a WCF web service being developed as the back end for a Silverlight/WPF client (assuming we're not using Ria services here) then your client uses/consumes your Web service.
I'm doing some work in the MVC world now and its dawned on me (after a conversation with a colleague) that you could/can have your "server" side services being consumed by your MVC model/controllers and the client, being web pages in html + javascript would never know. So some of our data now needs to be made public to other intranet apps and will be moved into web services. My question is should those web services be consumed by the MVC app, or should we continue to just call the services directly. Not really an issue if its all being hosted on the same web server but should someone down the track split the web services onto their own box it might make more sense. I guess it seems weird for me for an app to be developed with data that is not exposed via web services. (Silverlight/WPF pretty much is the only way to get at your data as all your calls are made from a client). Unless you are talking ajax calls or similar from the web browser, all this stuff is on the server. Perhaps the answer is "it depends"... interested in people's thoughts, ideas. enjoy your long weekend (if you have one) cheers, Stephen
