IpcChannel Constructor (IDictionary, IClientChannelSinkProvider, IServerChannelSinkProvider)
Initializes a new instance of the IpcChannel class with the specified configuration properties and sinks.
Assembly: System.Runtime.Remoting (in System.Runtime.Remoting.dll)
public IpcChannel( IDictionary properties, IClientChannelSinkProvider clientSinkProvider, IServerChannelSinkProvider serverSinkProvider )
- Type: System.Collections.IDictionary
A IDictionary collection specifying values for configuration properties to be used by the client and server channels.
- Type: System.Runtime.Remoting.Channels.IClientChannelSinkProvider
The IClientChannelSinkProvider implementation to be used by the client channel.
- Type: System.Runtime.Remoting.Channels.IServerChannelSinkProvider
The IServerChannelSinkProvider implementation to be used by the server channel.
For more information about channel configuration properties, see Channel and Formatter Configuration Properties.
Channel sinks provide a plug-in point that allows access to the underlying messages flowing through the channel as well as the stream used by the transport mechanism to send messages to a remote object. Channel sinks are also responsible for transporting messages between the client and the server. Channel sinks are linked together in a chain, and all channel messages flow through this chain of sinks before the message is finally serialized and transported. If you do not require sink functionality, set the clientSinkProvider and serverSinkProvider parameters to null.
When setting the exclusiveAddressUse property to false in the properties argument, several IpcServerChannel objects can be registered for the same named pipe. In such a case requests can go to any of the channels registered. This setting is considered secure only if ALCs are also used.
The following code example shows how to use this constructor. This code example is part of a larger example provided for the IpcChannel class.
- Full trust for the immediate caller. This member cannot be used by partially trusted code. For more information, see Using Libraries from Partially Trusted Code.
Windows 8.1, Windows Server 2012 R2, Windows 8, Windows Server 2012, Windows 7, Windows Vista SP2, Windows Server 2008 (Server Core Role not supported), Windows Server 2008 R2 (Server Core Role supported with SP1 or later; Itanium not supported)
The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.