Callbacks are also commonly referred to as duplex operations
Not all bindings support callback operations. Only bidirectional-capable bindings support callback operations.
For example, because of its connectionless nature, HTTP cannot be used for callbacks, and therefore you cannot use callbacks over the BasicHttpBinding or the WSHttpBinding.
The only two commonly used bindings that offer callbacks are the NetTcpBinding and the NetNamedPipeBinding, because by their very nature, the TCP and the IPC protocols support duplex communication.
To support callbacks over HTTP, WCF offers the WSDualHttpBinding, which actually
sets up two WS channels: one for the calls from the client to the service and one for the calls from the service to the client. But the NetTcpRelayBinding by and large deprecates the WSDualHttpBinding in the vast majority of callback cases.
For example, because of its connectionless nature, HTTP cannot be used for callbacks, and therefore you cannot use callbacks over the BasicHttpBinding or the WSHttpBinding.
The only two commonly used bindings that offer callbacks are the NetTcpBinding and the NetNamedPipeBinding, because by their very nature, the TCP and the IPC protocols support duplex communication.
To support callbacks over HTTP, WCF offers the WSDualHttpBinding, which actually
sets up two WS channels: one for the calls from the client to the service and one for the calls from the service to the client. But the NetTcpRelayBinding by and large deprecates the WSDualHttpBinding in the vast majority of callback cases.
댓글
댓글 쓰기