Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>When used with HTTP transport the server <em>does</em> call the client. In order to get this to work the client must be on a public endpoint, so firewalls and what-have-you will need to be configured appropriately.</p> <p>From <a href="http://msdn.microsoft.com/en-us/magazine/cc163537.aspx" rel="noreferrer">http://msdn.microsoft.com/en-us/magazine/cc163537.aspx</a>:</p> <blockquote> <p>Because of its connectionless nature, HTTP can't be used for callbacks and therefore you can't use callbacks over BasicHttpBinding or WSHttpBinding. Windows Communication Foundation offers callback support for NetTcpBinding and NetNamedPipeBinding because the underlying transport is bidirectional. To support callbacks over HTTP, Windows Communication Foundation provides WSDualHttpBinding, which actually sets up two HTTP channels: one for the calls from the client to the service and one for the calls from the service to the client.</p> </blockquote> <p>And from the reference for WSDualHttpBinding <a href="http://msdn.microsoft.com/en-us/library/system.servicemodel.wsdualhttpbinding.aspx" rel="noreferrer">http://msdn.microsoft.com/en-us/library/system.servicemodel.wsdualhttpbinding.aspx</a>:</p> <blockquote> <p>This binding requires that the client has a public URI that provides a callback endpoint for the service. This is provided by the ClientBaseAddress. A dual binding exposes the IP address of the client to the service. The client should use security to ensure that it only connects to services it trusts.</p> </blockquote>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload