Have you ever implemented a .NET remoting project? Were you satisfied with the default behavior of the remoting sinks? If not, did the content in this article help? Let us know in the csharp.general discussion group.
How to Build Custom Sink Providers for .NET Remoting
If the default remoting behavior doesn't suit your needs, change it! Leverage .NET Remoting and its extensible infrastructure to build customized message sinks that can help integrate your applications.
by Randy Holloway
July 2, 2003
he remoting framework in .NET contains a feature set designed to support intra-process communications and application integration functions; however, for many applications the default remoting behaviors may not deliver all the features that you need. For example, what if you want to implement an encryption scheme that secures the messaging layer for your remoting application? To do so, you can make both the client and the server application aware of the encryption and decryption requirements for the messages, but that will require some redundant code for both client and server that you can't easily leverage across applications. In contrast, using the extensibility features built into the .NET remoting framework lets you customize the remoting processes to suit your application's needs. This article shows you how to build a custom message serialization sink for a sample remoting application that captures SOAP messages and serializes data to the remoting client's file system.
Understanding .NET Remoting Infrastructure
To understand how to extend.NET remoting using custom sinks, you must first understand a little about how the remoting infrastructure works. The basic building blocks of the remoting architecture include:
It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com. Already a member?
To become a member of DevX.com create your Member Profile by completing the form below. Membership is free!
he remoting framework in .NET contains a feature set designed to support intra-process communications and application integration functions; however, for many applications the default remoting behaviors may not deliver all the features that you need. For example, what if you want to implement an encryption scheme that secures the messaging layer for your remoting application? To do so, you can make both the client and the server application aware of the encryption and decryption requirements for the messages, but that will require some redundant code for both client and server that you can't easily leverage across applications. In contrast, using the extensibility features built into the .NET remoting framework lets you customize the remoting processes to suit your application's needs. This article shows you how to build a custom message serialization sink for a sample remoting application that captures SOAP messages and serializes data to the remoting client's file system.
