. Net remoting common deployment structure

It was used some time ago. net remoting in the Internet, to use the TCP channel for higher performance, but there is no way to allow the firewall port (not 80), and finally use the second method below, http port 80, deploy remoting to IIS. Generally, the remoting structure can be divided into the following two types:

I,

Note:Remot object is the encapsulated business logic, and the server is the win ServerProgramIt is used to hold remote objects for the client to call. The client is a Web site and accesses the server through the TCP channel (a port must be provided. This Port cannot conflict with existing programs and cannot be intercepted by the firewall ). The client can directly operate on remote data by calling the server to obtain a remote object proxy locally.
It is more efficient to use the TCP channel, but the firewall needs to open the port used. You need to write a server program to carry remote objects.

II,

Note:Remot object is the encapsulated business logic. The server side is IIS. remote objects are loaded to IIS for calling. The client is a Web site and accesses the server over the HTTP channel (port 80 is used, the firewall allows this port ). The client can directly operate on remote data by calling the server to obtain a remote object proxy locally.
No additional server programs are required. remote objects are directly run in IIS (virtual directory). firewall issues are not considered when port 80 is used, and IIS is used to ensure better security; the efficiency of using HTTP channels is not as high as that of TCP channels.