public interface IChannel
|
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 IChannel.ChannelName and IChannel.ChannelPriority properties. Channels can be registered using the ChannelServices.RegisterChannel method.
ChannelName | Read-only Gets the name of the channel. |
ChannelPriority | Read-only Gets the priority of the channel. |
Parse | Returns the object URI as an out parameter, and the URI of the current channel as the return value. |
string ChannelName {get;}
|
int ChannelPriority {get;}
|
Client channels with higher priority are given the first chance to connect to a remote object specified by a URL or a particular channel data entry from an ObjRef.
For server channels, the priority indicates the order in which their channel data will appear in an ObjRef, which in turn affects the order in which clients will try to connect to the server object. If the server is listening on an HTTP channel with priority 50 and a TCP channel with priority 25 and the client has registered both an HTTP and TCP channel, then the client will use the HTTP channel to talk to the server.
url
objectURI