General Channel Properties
This topic is specific to a legacy technology that is retained for backward compatibility with existing applications and is not recommended for new development. Distributed applications should now be developed using the Windows Communication Foundation (WCF).
The following table describes the general channel properties and lists the channel types that support them.
| Property | Description | Types that support this property |
|---|---|---|
name |
A string that specifies the name of this channel. If you do not specify a name, a default name is used that depends on the type: HttpChannel: "http" HttpClientChannel: "http client" HttpServerChannel: "http server" TcpChannel: "tcp" TcpClientChannel: "tcp client" TcpServerChannel: "tcp server" IpcChannel: "ipc" IpcClientChannel: "ipc client" IpcServerChannel: "ipc server" Each channel must have a unique name. Set this property to an empty string ("" or String.Empty) if you want to ignore names, but avoid naming collisions. The system allows any number of channels with name equal to String.Empty. This property is used to retrieve a specific channel when calling ChannelServices.GetChannel. For more information, see Channels. |
|
machineName |
A string that specifies the machine name used with the current channel. If used with a server channel, overrides useIpAddress. .gif "Note") Note
It is generally a good idea to use the Domain Name System (DNS) name of the computer, but when the IP Address for a particular network interface card (NIC) (usually a wireless NIC) is changing rapidly, you must configure the application to use the machineName to enable remoting to find the machine through DNS. However, when the computer name does not resolve with reasonable speed (if at all) and when the computer has more than one NIC, either physical or virtual (this is often the case with a dial-up connection or VPN network adapter), you should set the machineName property to the IP address of the NIC that is currently in use for that connection.
|
HttpChannel HttpClientChannel HttpServerChannel TcpChannel TcpClientChannel TcpServerChannel |
priority |
An integer that represents the priority assigned to this channel. Higher numbers indicate a higher chance of being chosen to connect first. The default priority is 1, and negative numbers are allowed. |
HttpChannel HttpServerChannel HttpClientChannel TcpChannel TcpClientChannel TcpServerChannel IpcChannel IpcClientChannel IpcServerChannel |
secure (TcpChannel) |
A Boolean value (true or false) that specifies whether communications on the channel are secure. The default is false. When it is set to true, the tokenImpersonationLevel property is set to Identification and the protectionLevel property is set to EncryptAndSign. Note that a secure TcpClientChannel may connect only to a secure TcpServerChannel, and a non-secure TcpClientChannel may connect only to a non-secure TcpServerChannel. Note
If the server computer is running Windows 95, Windows 98, or Windows Me, the TcpServerChannel cannot be specified as secure.
|
TcpChannel TcpClientChannel TcpServerChannel |
secure (IpcChannel) |
A Boolean value (true or false) that specifies whether communications on the channel are secure. The default is false. When it is set to true, the tokenImpersonationLevel property is set to Identification. Note that a secure IpcClientChannel may connect to either a secure or non-secure IpcServerChannel, but a non-secure IpcClientChannel may connect only to a non-secure IpcServerChannel. |
IpcChannel IpcClientChannel IpcServerChannel |
protectionLevel |
A value of type ProtectionLevel. The default is None, unless the secure property is set to true, in which case the default is EncryptAndSign. You must set the secure property to true to set the ProtectionLevel property to any value other than None. Note that None is the only setting that is compatible with Windows 95, Windows 98, or Windows Me. |
TcpClientChannel TcpServerChannel |
See Also
Tasks
How to: Configure a Channel in a Configuration File
How to: Configure a Channel Programmatically
Reference
Concepts
Configuration of Remote Applications
Remote Object Configuration
Remote Object Configuration