This documentation is archived and is not being maintained.

IpcServerChannel Class

Implements a server channel for remote calls that uses the IPC system to transmit messages.

Namespace: System.Runtime.Remoting.Channels.Ipc
Assembly: System.Runtime.Remoting (in system.runtime.remoting.dll)

public class IpcServerChannel : IChannelReceiver, IChannel, ISecurableChannel
public class IpcServerChannel implements IChannelReceiver, IChannel, 
	ISecurableChannel
public class IpcServerChannel implements IChannelReceiver, IChannel, 
	ISecurableChannel
Not applicable.

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 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 IServerChannelSinkProvider interface through which all messages processed by the IpcServerChannel instance are passed.

The IpcServerChannel instance accepts messages serialized in either binary or SOAP format.

A IpcServerChannel object has associated configuration properties that can be set at run time either in a configuration file (by invoking the static RemotingConfiguration.Configure method) or programmatically (by passing an IDictionary collection to the IpcServerChannel constructor). For a list of these configuration properties, see the documentation for the IpcServerChannel constructor.

Caution noteCaution:

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 illustrates how to use the IpcServerChannel class.

using System;
using System.Runtime.Remoting;
using System.Runtime.Remoting.Channels;
using System.Runtime.Remoting.Channels.Ipc;

public class IpcServer
{

    public static void Main ()
    {
        // Create and register an IPC channel
        IpcServerChannel serverChannel = new IpcServerChannel("remote");
        ChannelServices.RegisterChannel(serverChannel);

        // Expose an object
        RemotingConfiguration.RegisterWellKnownServiceType( typeof(Counter), "counter", WellKnownObjectMode.Singleton );

        // Wait for calls
        Console.WriteLine("Listening on {0}", serverChannel.GetChannelUri());
        Console.ReadLine();
    }

}

import System.*;
import System.Runtime.Remoting.*;
import System.Runtime.Remoting.Channels.*;
import System.Runtime.Remoting.Channels.Ipc.*;

public class IpcServer
{
    public static void main(String[] args)
    {
        // Create and register an IPC channel
        IpcServerChannel serverChannel = new IpcServerChannel("remote");
        ChannelServices.RegisterChannel(serverChannel);
        // Expose an object
        RemotingConfiguration.RegisterWellKnownServiceType(
            Counter.class.ToType(), "counter", WellKnownObjectMode.Singleton);
        // Wait for calls
        Console.WriteLine("Listening on {0}", serverChannel.GetChannelUri());
        Console.ReadLine();
    } //main
} //IpcServer 

The preceding code is used to expose the following remote object.

using System;

public class Counter : MarshalByRefObject {

  private int count = 0;

  public int Count { get {
    return(count++);
  } }

}

import System.*;

public class Counter extends MarshalByRefObject
{
    private int count = 0;

    /** @property 
     */
    public int get_Count()
    {
        return count++;
    } //get_Count
} //Counter 

For an example of a client using this object remotely, see IpcClientChannel.

System.Object
  System.Runtime.Remoting.Channels.Ipc.IpcServerChannel

Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.

Windows 98, Windows Server 2000 SP4, Windows Millennium Edition, Windows Server 2003, Windows XP Media Center Edition, Windows XP Professional x64 Edition, Windows XP SP2, Windows XP Starter Edition

The Microsoft .NET Framework 3.0 is supported on Windows Vista, Microsoft Windows XP SP2, and Windows Server 2003 SP1.

.NET Framework

Supported in: 3.0, 2.0
Show: