.NET Remoting
.NET Remoting is a Microsoft application programming interface (API) for interprocess communication released in 2002 with the 1.0 version of .NET Framework. It is one in a series of Microsoft technologies that began in 1990 with the first version of Object Linking and Embedding (OLE) for 16-bit Windows. Intermediate steps in the development of these technologies were Component Object Model (COM) released in 1993 and updated in 1995 as COM-95, Distributed Component Object Model (DCOM), released in 1997 (and renamed Active X), and COM+ with its Microsoft Transaction Server (MTS), released in 2000.[1] It is now superseded by Windows Communication Foundation (WCF), which is part of the .NET Framework 3.0.
Like its family members and similar technologies such as Common Object Request Broker Architecture (CORBA) and Java's remote method invocation (RMI), .NET Remoting is complex, yet its essence is straightforward. With the assistance of operating system and network agents, a client process sends a message to a server process and receives a reply.[2][3]
Overview
.NET Remoting allows an application to make an object (termed remotable object) available across remoting boundaries, which includes different appdomains, processes or even different computers connected by a network.[4] The .NET Remoting runtime hosts the listener for requests to the obj
References
- ^ Software Technology Roadmap (2001). "Component Object Model and Related Capabilities". Carnegie-Mellon Software Engineering Institute.
{{cite web}}: Missing or empty|url=(help) - ^ Scott McLean, James Naftel and Kim Williams (2002). Microsoft .NET Remoting. Microsoft Press.
- ^ Ingo Rammer and Mario Szpuszta (2005). Advanced .NET Remoting. Apress.
- ^ Cite error: The named reference
overviewwas invoked but never defined (see the help page).
