Chapter 11. .NET Remoting

I l @ ve RuBoard

The Microsoft .NET Remoting architecture lets you construct distributed solutions based on high-level network abstractions such as remote procedure calls (RPCs), serialization, and messaging. You can create and deploy server applications almost anywhere on your network, or even over the Internet, and connect to them from client applications reliably and securely using the infrastructure supplied by the .NET platform.

Remoting uses the familiar concept of proxy objects. Clients communicate with proxies, which in turn communicate with real server objects. The proxy hides the complexities of distributed activation from the client, making a remote object as easy to access as a local one. You can modify the way in which proxies send requests from a client to a server by implementing a custom marshaling strategy. Server objects can be hosted by .NET applications or by Microsoft Internet Information Services (IIS) version 6.0 or later. The implementation of the .NET Remoting infrastructure uses TCP and HTTP as transport protocols. If you need to use a different protocol ”for communicating with a legacy server, for example ”you can implement your own communications channel.

The mechanisms used by .NET Remoting are very flexible. You can extend them if the default implementation of the various components does not match your requirements. In this chapter, we'll look at how you can use the .NET Remoting architecture for communicating between clients and remote servers and how you can customize it.

I l @ ve RuBoard