The .net remote systems
Download as PPTX, PDF0 likes341 views
The document discusses .NET Remoting and how it enables communication between .NET applications. It compares .NET Remoting to other technologies like DCOM and web services, noting they have some similarities but also differences in their goals and implementations. Specifically, .NET Remoting provides an abstract approach to interprocess communication, while web services represent a concrete XML-based implementation of that approach. The document also positions .NET Remoting as an improvement over DCOM, which it replaces as the technology for remote communication between Windows applications.
The .net remote systems
- 2. The Microsoft .NET Framework infrastructure for remoting is the set of system services that enable .NET applications to communicate and exchange data and objects.
- 3. Interprocess Communications in the .NET Framework Web services and .NET Remoting are distinct, stand-alone technologies that share a common root but have different sets of features and, more important, different goals. Both Web services and .NET Remoting let you publish functions over a network and handle incoming calls. Both share an architectural design that includes layers for request/response handling, object serialization, and data transportation. Both share underlying network protocols such as Simple Object Access Protocol (SOAP) and HTTP.
- 4. Overall, Web services and .NET Remoting are two distinct and independent sides of the same coin. Web services—a clearly XML-based technology—are a special case of the .NET Remoting infrastructure. The .NET Framework infrastructure for remoting can be seen as an abstract approach to interprocess communication. Web services and .NET Remoting are technologies that represent concrete implementations of that abstract interface. As distinct implementations, they end up using different building blocks to set up constituent features such as object serialization, type description, and reflection. The actual underlying technologies that make Web services and .NET Remoting happen are chosen according to the final goal of each technology.
- 5. .NET Remoting as a Better DCOM Prior to the advent of the .NET Framework, DCOM was the underlying technology of choice for any sort of remote communication between Microsoft Windows applications. Based on a proprietary binary protocol, DCOM has suffered since its conception from a number of shortcomings. For this reason, DCOM never charmed its way into the average programmer's heart, although it did prove to be functional and effective. DCOM is somewhat quirky to set up and configure, and under certain, but relatively frequent, circumstances, it also raises serious interoperability exceptions that basically put you in the unenviable position of having to change the connectivity engine for the sake of the application or simply give up.
- 6. DCOM Extensions for the Internet Over the years, DCOM has been extended to work around this security issue. In particular, the COM Internet Services (CIS) layer has given DCOM the capability to work over port 80 thanks to a new transportation protocol called Tunneling Transmission Control Protocol (TTCP). CIS works as an Internet Server Application Programming Interface (ISAPI) filter and requires Microsoft Internet Information Services (IIS) 4.0 or later to run on the server machine. Basically, TTCP works by fooling the firewall. At the very beginning of each DCOM operation, TTCP shakes hands with the server, declaring its intention to use HTTP over port 80.
- 7. What Is .NET Remoting? The entire set of services that enable .NET Framework applications to communicate with each other falls under the umbrella of .NET Remoting. Such applications can reside on the same computer, can work on different computers in the same LAN, and can even be scattered across the world in heterogeneous networks but on homogeneous platforms—that is, platforms that can host the common language runtime (CLR) and access the .NET Framework.