Extending .NET Remoting
Ingo Rammer · Apress eBooks · 2002
In chapters 7 and 8 , I told you a lot about the various places that can be extended by custom sinks and providers. What I didn’t tell you is why you’d want to change the default remoting behavior. There are a lot of reasons for doing so: Compression or encryption of the message’s contents Passing additional information from the client to the server. For example, you could pass the client-side thread’s priority to the server so that the remote execution is performed using the same priority Extending the look and feel of.NET Remoting. You could, for example, switch to a per-host authentication model instead of the default per-object model. Debugging your applications by dumping the message’s contents to the console or to a log file. And last but not least, custom sinks and providers enable you to use other transport mediums such as MSMQ or even SMTP/POP3 These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.