Conclusion

I l @ ve RuBoard

Both Web services and remoting provide a wealth of features for applications. Your choice should be based purely on design considerations. Web services work well in an environment in which you have to consider supporting diverse platforms. SOAP is, after all, an open standard, and Web services can be consumed by any platform that understands the Microsoft WebServices XML schema. Web services also provide a great deal of scalability and performance features, thanks to IIS.

Remoting is obviously more platform-centric, but it provides for the more generic interapplication communication scenarios. Combining speed with less overhead, remoting definitely fits the bill for local interapplication communication. When a distributed network is involved, you have the option of hosting your remote objects in IIS to improve performance as well as gain scalability features. In addition, the ability to use a variety of communication channels is extremely powerful and can accommodate all sorts of custom remoting scenarios.

In the end, you must choose the solution that best fits your application's needs. Remoting and Web services are not always mutually exclusive options, so you can also use them in concert if necessary.

I l @ ve RuBoard