Comparison Between. Net remoting and Web Service

After the comparison between. Net remoting and Web Service comes out of WCF, these two are basically the artifacts of the antique heap. Write them down to prevent them from being completely forgotten.

In a macro sense, Web Service is a cross-platform thing. From IIS,. Net remoting calls each other within the Microsoft framework.

A. Performance
. Net remoting binary formatter and TCP channel are the fastest, ASP. NET web service is not the slowest, and the slowest is. Net remoting soap formatter HTTP channel.

B. Status Management
The Web Service is stateless. . Net remoting depends on which connection method. Single call is not in the status. Singleton shares the status among several clients. The client-activated has its own status on each client.

C. Security
. Net remoting needs to maintain its own status. Web Service and IIS can use SSL and authentication.

D. Reliability
Web service can borrow IIS thread security, Automatic startup, and so on. NET remoting should be determined by yourself.

E. Easy Programming
Web Service is relatively easy.. Net remoting needs to write config and construct an object, which is more complex.

In short, the Web service is better if there are many cross-platform interactions and must be implemented through the public network. If you want to interact with other. NET components and want better performance, remoting is better.