locked
Message between wshttpbinding and httpbinding RRS feed

  • Question

  • User1849788689 posted
    Hi to all,

    I have a presentation tomorrow regarding to wcf, and i want to show them what is the difference between httpbinding and wshttpbinding when the message is sent, may i know the tool to be use. Much better if the software is free
    Tuesday, October 15, 2013 9:28 AM

Answers

  • User260886948 posted

    Hi,

    It seems that want to know the  differences  betwwen BasicHttpBinding  , WsHttpBinding and WebHttpBinding . If so, please try to refer to the following:

    You're comparing apples to oranges here:

    • webHttpBinding is the REST-style binding, where you basically just hit a URL and get back a truckload of XML or JSON from the web service

    • basicHttpBinding and wsHttpBinding are two SOAP-based bindings which is quite different from REST. SOAP has the advantage of having WSDL and XSD to describe the service, its methods, and the data being passed around in great detail (REST doesn't have anything like that - yet). On the other hand, you can't just browse to a wsHttpBinding endpoint with your browser and look at XML - you have to use a SOAP client, e.g. the WcfTestClient or your own app.

    So your first decision must be: REST vs. SOAP (or you can expose both types of endpoints from your service - that's possible, too).

    Then, between basicHttpBinding and wsHttpBinding, there differences are as follows:

    • basicHttpBinding is the very basic binding - SOAP 1.1, not much in terms of security, not much else in terms of features - but compatible to just about any SOAP client out there --> great for interoperability, weak on features and security

    • wsHttpBinding is the full-blown binding, which supports a ton of WS-* features and standards - it has lots more security features, you can use sessionful connections, you can use reliable messaging, you can use transactional control  - just a lot more stuff, but wsHttpBinding is also a lot *heavier" and adds a lot of overhead to your messages as they travel across the network

    For an in-depth comparison (including a table and code examples) between the two check out this codeproject article: Differences between BasicHttpBinding and WsHttpBinding 

    Best Regards,
    Amy Peng

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Wednesday, October 16, 2013 3:26 AM
  • User503812343 posted

    Binding with Http protocol basically use for communication with HTTP like web applications.  

    in WCF httpBinding is best suitable when you have to replace old asmx based web services with flexibility and features of WCF.

    wsHttpBinding supports WS* standards and provides security, sessions, transctions etc.

    for more information on when to use which binding in WCF

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Wednesday, October 16, 2013 2:37 PM
    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Wednesday, October 16, 2013 10:25 PM

All replies

  • User260886948 posted

    Hi,

    It seems that want to know the  differences  betwwen BasicHttpBinding  , WsHttpBinding and WebHttpBinding . If so, please try to refer to the following:

    You're comparing apples to oranges here:

    • webHttpBinding is the REST-style binding, where you basically just hit a URL and get back a truckload of XML or JSON from the web service

    • basicHttpBinding and wsHttpBinding are two SOAP-based bindings which is quite different from REST. SOAP has the advantage of having WSDL and XSD to describe the service, its methods, and the data being passed around in great detail (REST doesn't have anything like that - yet). On the other hand, you can't just browse to a wsHttpBinding endpoint with your browser and look at XML - you have to use a SOAP client, e.g. the WcfTestClient or your own app.

    So your first decision must be: REST vs. SOAP (or you can expose both types of endpoints from your service - that's possible, too).

    Then, between basicHttpBinding and wsHttpBinding, there differences are as follows:

    • basicHttpBinding is the very basic binding - SOAP 1.1, not much in terms of security, not much else in terms of features - but compatible to just about any SOAP client out there --> great for interoperability, weak on features and security

    • wsHttpBinding is the full-blown binding, which supports a ton of WS-* features and standards - it has lots more security features, you can use sessionful connections, you can use reliable messaging, you can use transactional control  - just a lot more stuff, but wsHttpBinding is also a lot *heavier" and adds a lot of overhead to your messages as they travel across the network

    For an in-depth comparison (including a table and code examples) between the two check out this codeproject article: Differences between BasicHttpBinding and WsHttpBinding 

    Best Regards,
    Amy Peng

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Wednesday, October 16, 2013 3:26 AM
  • User503812343 posted

    Binding with Http protocol basically use for communication with HTTP like web applications.  

    in WCF httpBinding is best suitable when you have to replace old asmx based web services with flexibility and features of WCF.

    wsHttpBinding supports WS* standards and provides security, sessions, transctions etc.

    for more information on when to use which binding in WCF

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Wednesday, October 16, 2013 2:37 PM
    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Wednesday, October 16, 2013 10:25 PM