One of Microsoft's Remoting framework. NET Remoting (Turn Tenkine)

Microsoft's. NET Remoting provides a framework that allows an object to interact with another object through an application domain. This article introduces its features through two specific code examples, with the. NET Remoting, the communication between the two applications will be very simple and very flexible to use. <br>
<br>
<br>
In recent years, in the computer world, there has been a constant discussion of "outward extension" (scale-out) and "Upward expansion" (scale-up), and there has been a tendency towards scale-out transformation. In the past, when computers couldn't keep up with the performance requirements, people would buy a better and more expensive machine, which was scale-up, and Scale-out would be able to solve the problem by adding more machines to the network without replacing the entire system. By assigning the burden of computation to multiple systems, the entire system has a higher availability. <br>
<br>
If we take this scale-out idea a step further, we may find that: why should we put the processing of credit card verification and delivery tracking on our system? Wouldn't it be easier if we could invoke the application of the seller to get the services directly? If we can do this, we can expand the functionality of our programs without having to add additional hardware. It is noteworthy that this will transform the role of an ISV (independent software developer) from a software provider to a service provider. <br>
<br>
This idea is very good, but the current technology to achieve it, there are a lot of problems. DCOM can be problematic when working across firewalls. DCOM is based on the private protocol, while CORBA has many problems with different interfaces. It would be even more troublesome if DCOM and CORBA were put together. <br>
<br>
To realize this scale-out idea, we need a component technology that can work seamlessly across multiple types of networks and protocols. Remote. NET can do this. <br>
<br>
This seamless interaction is achieved through the use of XML and SOAP. However, it does not recognize soap as the only way to interact with components, nor does it determine that HTTP or TCP/IP is the network protocol used to connect these services. This will make the remote architecture more flexible and adaptable to protocol and network changes. <br>
<br>
. NET schemas are used to connect applications together using the channel object. NET architecture proposes two kinds of channel, they are:<br>
<br>
System.runtime.remoting.channels.tcp<br>
System.Runtime.Remoting.Channels.HTTP <br>
<br>
TCP channel is very similar to existing DCOM, providing a high performance that allows TCP channel to be selected while the machine is in an internal network, while HTTP channel uses the HTTP protocol to allow applications to interact on the Internet. Because it uses the HTTP protocol, it can easily load-balance and pass through the firewall.