If we want to summarize in one sentence, the difference between WsHttpBinding and BasicHttpBinding is that WsHttpBinding supports WS-* specification. WS-* specifications are nothing but standards to extend web service capabilities.
Below is a detailed comparison table between both the entities from security, compatibility, reliability and SOAP version perspective.
|Security support||This supports the old ASMX style, i.e. WS-BasicProfile 1.1.||This exposes web services using WS-* specifications.|
|Compatibility||This is aimed for clients who do not have .NET 3.0 installed and it supports wider ranges of clients. Many of the clients like Windows 2000 still do not run .NET 3.0. So older version of .NET can consume this service.||As its built using WS-* specifications, it does not support wider ranges of client and it cannot be consumed by older .NET version less than 3 version.|
|Soap version||SOAP 1.1||SOAP 1.2 and WS-Addressing specification.|
|Reliable messaging||Not supported. In other words, if a client fires two or three calls you really do not know if they will return back in the same order.||Supported as it supports WS-* specifications.|
|Default security options||By default, there is no security provided for messages when the client calls happen. In other words, data is sent as plain text.||As |
One of the biggest differences you must have noticed is the security aspect. By default,
BasicHttpBinding sends data in plain text while
WsHttpBinding sends it in encrypted and secured manner.
To demonstrate the same, lets make two services, one using
BasicHttpBinding and the other using
WsHttpBinding and then lets see the security aspect in a more detailed manner.
Source : www.codeproject.com
Hope this will help you!