This documentation is archived and is not being maintained.

IChannel Interface

Provides conduits for messages that cross remoting boundaries.

For a list of all members of this type, see IChannel Members.

[Visual Basic]
Public Interface IChannel
[C#]
public interface IChannel
[C++]
public __gc __interface IChannel
[JScript]
public interface IChannel

Classes that Implement IChannel

Class Description
HttpChannel Provides an implementation for a sender-receiver channel that uses the HTTP protocol to transmit messages.
HttpClientChannel Provides an implementation for a client channel that uses the HTTP protocol to transmit messages.
HttpServerChannel Provides an implementation for a server channel that uses the HTTP protocol to transmit messages.
TcpChannel Provides an implementation for a sender-receiver channel that uses the TCP protocol to transmit messages.
TcpClientChannel Provides an implementation for a client channel that uses the TCP protocol to transmit messages.
TcpServerChannel Provides an implementation for a server channel that uses the TCP protocol to transmit messages.

Remarks

Remoting boundaries can be Context s, AppDomain s, processes, or computers. An application can cross these boundaries only by using channels. These crossings can be inbound and outbound. A channel can listen on an endpoint for inbound messages, send to an endpoint for outbound messages, or both. This provides an extensibility point in the runtime to plug in a wide range protocols, even though the runtime might not be at the other end of the channel.

Run-time objects can be used to represent a wide and rich set of semantics and entities. The channel provides the extensibility point to convert the messages to and from the specific protocols. If there are runtimes at both ends of the channel, a virtual channel is created between the two ends, in order to connect the client and server sink chains on either side of the boundary.

The client part of the channel is located at the end of a client context sink chain. The server part of the channel is located at the start of the server context sink chain. Messages are delivered to the client channel using the IMessageSink interface, travel through the channel, and are then received by the server channel. The server channel delivers the message to the first server context sink.

Channels must expose the IChannel interface, which provides informational properties such as the ChannelName and ChannelPriority properties. Channels can be registered using the ChannelServices.RegisterChannel method.

Requirements

Namespace: System.Runtime.Remoting.Channels

Platforms: Windows 98, Windows NT 4.0, Windows Millennium Edition, Windows 2000, Windows XP Home Edition, Windows XP Professional, Windows Server 2003 family

Assembly: Mscorlib (in Mscorlib.dll)

See Also

IChannel Members | System.Runtime.Remoting.Channels Namespace

Show: