See Also: IpcServerChannel Members
Channels are used by the .NET Framework remoting infrastructure to transport remote calls. When a client calls a remote object, the call is serialized into a message that is sent by a client channel and received by a server channel. After the message is received, it is deserialized and processed. Any returned values are transmitted by the server channel and received by the client channel.
The System.Runtime.Remoting.Channels.Ipc.IpcServerChannel class uses the Windows interprocess communication (IPC) system to transport messages between application domains on the same computer. When communicating between application domains on the same computer, the IPC channel is much faster than the TCP or HTTP channels.
To perform additional processing of messages on the server side, specify an implementation of the System.Runtime.Remoting.Channels.IServerChannelSinkProvider interface through which all messages processed by the System.Runtime.Remoting.Channels.Ipc.IpcServerChannel instance are passed.
The System.Runtime.Remoting.Channels.Ipc.IpcServerChannel instance accepts messages serialized in either binary or SOAP format.
A System.Runtime.Remoting.Channels.Ipc.IpcServerChannel object has associated configuration properties that can be set at run time either in a configuration file (by invoking the static System.Runtime.Remoting.RemotingConfiguration.Configure(string) method) or programmatically (by passing an IDictionary collection to the IpcServerChannel.#ctor(IDictionary, System.Runtime.Remoting.Channels.IServerChannelSinkProvider) constructor). For a list of these configuration properties, see the documentation for the IpcServerChannel.#ctor(IDictionary, System.Runtime.Remoting.Channels.IServerChannelSinkProvider) constructor.
When setting the exclusiveAddressUse property to false in the properties argument, several System.Runtime.Remoting.Channels.Ipc.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.