"Yes, you're probably right about remoting being faster, but I think it was just easier to do it all with Web Services and not have to worry about allowing the front-end to communicate both ways. <g> Besides, by using Web Services, we've opened up some of the functionality to other users besides just our application."


Hey, Bonnie,

Yeah, there's no question that web services are easier to deal with, and more 'open'. I struggled learning SOAP a few years ago, so Web Services in .NET were a god-send for me.

IMO, the only time remoting is absolutely necessary is when a company insists that the web server and application logic reside on totally different spots. In that instance, the best way for the web server to execute the business layer code on the business server was to use remoting.

While it wasn't necessary for the internal users to remote with the app server, we put the support in anyway. They had been using a VFP desktop version for years, and the perceived 'bottleneck' of going through the web service (even w/an internal IP address) was such that we put the support in for remoting, to head off any backlash. Since we had already developed a remoting client/proxy for the web service anyway, it wasn't that big a deal.

I've heard rumors from multiple sources about MS wanting to 'eliminate' remoting and push web services even harder in the future. But until they can convince hundreds of I.S. heads that installing multiple instances of I.I.S. is practical, that doesn't seem like a wise move.

Kevin