| UID | title | description | helpviewer_keywords | old-location | tech.root | ms.assetid | ms.date | ms.keywords | req.header | req.include-header | req.target-type | req.target-min-winverclnt | req.target-min-winversvr | req.kmdf-ver | req.umdf-ver | req.ddi-compliance | req.unicode-ansi | req.idl | req.max-support | req.namespace | req.assembly | req.type-library | req.lib | req.dll | req.irql | targetos | req.typenames | req.redist | ms.custom | f1_keywords | dev_langs | topic_type | api_type | api_location | api_name | ||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NE:webservices.WS_CHANNEL_TYPE |
WS_CHANNEL_TYPE (webservices.h) |
Indicates the basic characteristics of the channel, such as whether it is sessionful, and what directions of communication are supported. |
|
wsw\ws_channel_type.htm |
wsw |
7e1092f9-10e8-485c-a286-770e1c74d8ca |
12/05/2018 |
WS_CHANNEL_TYPE, WS_CHANNEL_TYPE enumeration [Web Services for Windows], WS_CHANNEL_TYPE_DUPLEX, WS_CHANNEL_TYPE_DUPLEX_SESSION, WS_CHANNEL_TYPE_INPUT, WS_CHANNEL_TYPE_INPUT_SESSION, WS_CHANNEL_TYPE_OUTPUT, WS_CHANNEL_TYPE_OUTPUT_SESSION, WS_CHANNEL_TYPE_REPLY, WS_CHANNEL_TYPE_REQUEST, WS_CHANNEL_TYPE_SESSION, webservices/WS_CHANNEL_TYPE, webservices/WS_CHANNEL_TYPE_DUPLEX, webservices/WS_CHANNEL_TYPE_DUPLEX_SESSION, webservices/WS_CHANNEL_TYPE_INPUT, webservices/WS_CHANNEL_TYPE_INPUT_SESSION, webservices/WS_CHANNEL_TYPE_OUTPUT, webservices/WS_CHANNEL_TYPE_OUTPUT_SESSION, webservices/WS_CHANNEL_TYPE_REPLY, webservices/WS_CHANNEL_TYPE_REQUEST, webservices/WS_CHANNEL_TYPE_SESSION, wsw.ws_channel_type |
webservices.h |
Windows |
Windows 7 [desktop apps \| UWP apps] |
Windows Server 2008 R2 [desktop apps \| UWP apps] |
Windows |
WS_CHANNEL_TYPE |
19H1 |
|
|
|
|
|
|
Indicates the basic characteristics of the channel, such as whether it is sessionful, and what directions of communication are supported.
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.
Output channels support Send operations.
This channel type is not currently supported by any channel bindings.
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.
An input channel that supports a session.
This channel type is not currently supported by any channel bindings.
An output channel that supports a session.
This channel type is not currently supported by any channel bindings.
An input/output channel.
The WS_UDP_CHANNEL_BINDING supports this channel type when used with WsCreateChannel.
An input/output channel that supports a session.
The WS_TCP_CHANNEL_BINDING supports this channel type when used with WsCreateChannel or WsCreateChannelForListener.
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).
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).