WS_CHANNEL_TYPE enumeration
Indicates the basic characteristics of the channel, such as whether it is sessionful, and what directions of communication are supported.
Syntax
enum WS_CHANNEL_TYPE { WS_CHANNEL_TYPE_INPUT = 0x1,
WS_CHANNEL_TYPE_OUTPUT = 0x2,
WS_CHANNEL_TYPE_SESSION = 0x4,
WS_CHANNEL_TYPE_INPUT_SESSION = WS_CHANNEL_TYPE_INPUT | WS_CHANNEL_TYPE_SESSION,
WS_CHANNEL_TYPE_OUTPUT_SESSION = WS_CHANNEL_TYPE_OUTPUT | WS_CHANNEL_TYPE_SESSION,
WS_CHANNEL_TYPE_DUPLEX = WS_CHANNEL_TYPE_INPUT | WS_CHANNEL_TYPE_OUTPUT,
WS_CHANNEL_TYPE_DUPLEX_SESSION = WS_CHANNEL_TYPE_INPUT | WS_CHANNEL_TYPE_OUTPUT | WS_CHANNEL_TYPE_SESSION,
WS_CHANNEL_TYPE_REQUEST = 0x8,
WS_CHANNEL_TYPE_REPLY = 0x10
};
Constants
- WS_CHANNEL_TYPE_INPUT
-
Input channels support Receive operations. They are used on the sender side.
The WS_UDP_CHANNEL_BINDING supports this channel type when used with WsCreateChannelForListener.
- WS_CHANNEL_TYPE_OUTPUT
-
Output channels support Send operations.
This channel type is not currently supported by any channel bindings.
- WS_CHANNEL_TYPE_SESSION
-
Sessionful channels provide channel-level correlation of all messages sent or received.
This is a flag used to build WS_CHANNEL_TYPE_INPUT_SESSION, WS_CHANNEL_TYPE_OUTPUT_SESSION, and WS_CHANNEL_TYPE_DUPLEX_SESSION, but cannot be used alone.
- WS_CHANNEL_TYPE_INPUT_SESSION
-
An input channel that supports a session.
This channel type is not currently supported by any channel bindings.
- WS_CHANNEL_TYPE_OUTPUT_SESSION
-
An output channel that supports a session.
This channel type is not currently supported by any channel bindings.
- WS_CHANNEL_TYPE_DUPLEX
-
An input/output channel.
The WS_UDP_CHANNEL_BINDING supports this channel type when used with WsCreateChannel.
- WS_CHANNEL_TYPE_DUPLEX_SESSION
-
An input/output channel that supports a session.
The WS_TCP_CHANNEL_BINDING supports this channel type when used with WsCreateChannel or WsCreateChannelForListener.
- WS_CHANNEL_TYPE_REQUEST
-
Request channels support Send followed by Receive. They are used on the client side for channels that support request-reply operations.
The WS_HTTP_CHANNEL_BINDING supports this channel type when used with WsCreateChannel.
Note that request channels provide built-in correlation of request replies. It is possible to do request-reply correlation on other channel types using the addressing headers (RelatesTo and MessageID).
- WS_CHANNEL_TYPE_REPLY
-
Reply channels support Receive followed by Send. They are used on the service side for channels that support request-reply operations (for example, HTTP).
The WS_HTTP_CHANNEL_BINDING supports this channel type when used with WsCreateChannelForListener.
Note that reply channels provide built-in correlation of request replies. It is possible to do request-reply correlation on other channel types using the addressing headers (RelatesTo and MessageID).
Requirements
|
Minimum supported client | Windows 7 [desktop apps | Windows Store apps] |
|---|---|
|
Minimum supported server | Windows Server 2008 R2 [desktop apps | Windows Store apps] |
|
Header |
|