This project is read-only.

If You Need to Support Clients Over the Internet, Consider Using wsHttpBinding

- J.D. Meier, Carlos Farre, Jason Taylor, Prashant Bansode, Steve Gregersen, Madhu Sundararajan, Rob Boucher

If your service will be called by clients over the Internet, consider using the wsHttpBinding. wsHttpBinding is a good choice for Internet scenarios in which you do not have to support legacy clients which expect an ASMX web service. If you do need to support legacy clients, consider using basicHttpBinding instead.

The wsHttpBinding has the following characteristics:
  • Provides interoperability with non-wcf clients that support the ws* stack.
  • Supports the WS* stack including reliable messaging, message security, and secure transactions.
  • Message security is turned on by default, transport security is also available.
  • Allows the service to be hosted in IIS 5 or IIS 6.
  • If you choose transport security you can use certificates, Windows, or token authentication.
  • If you choose message security you can use certificates, Username, Windows, or Issue token authentication (Windows CardSpace).

The following example shows how to configure wsHttpBinding :
<system.serviceModel>
....
    <services>
        <service behaviorConfiguration="" name="WCFServicecHost.MyService">
            ...
            <endpoint address="" binding="wsHttpBinding" bindingConfiguration=""
                name="wsBinding" contract="WCFServicecHost.IMyService" />
            ...
        </service>
    </services>
</system.serviceModel>

Additional Resources

Last edited Jun 12, 2008 at 10:10 PM by prashantbansode, version 1

Comments

No comments yet.