Reputation: 31493
When writing a new SOAP web service why would I choose to use version 1.2 over 1.1?
The numerous technologies for writing SOAP web services allow me to create services which adhere to either SOAP 1.1 or 1.2. It's not clear to me what benefits 1.2 provides over and above 1.1. This leads me to the conclusion that I should always use 1.1 to accommodate the largest number of compatible clients.
Why would I choose to create a SOAP 1.2 rather than a SOAP 1.1 web service?
Upvotes: 1
Views: 1203
Answers (1)
Reputation: 10309
From practical standpoint this is the case when you don't need SOAP1.2 if you're happy with 1.1, at least for now.
1.2 is quite different standard, its messages are infoset-based and (most notably) it is protocol-agnostic (you can use your own binary protocol for message delivery) and it is not backwards-compatible with 1.1.
You could read more here. Note the "Related information" section.
Upvotes: 3
Related Questions
- Magento SOAP v1 vs. v2 performance
- Producing SOAP webservices with spring-ws with Soap v1.2 instead of the default v1.1
- Can both SOAP 1.1 and 1.2 supported by a web service
- SOAP1.1 or SOAP1.2
- Can a WSDL indicate the SOAP version (1.1 or 1.2) of the web service?
- Should I use WSDL specification 1.1 or 2.0?
- Magento:: What is the difference between soap API version 1 and 2?
- Versioning SOAP body vs entire service?
- why soap web services
- Using a SOAP 1.1 web service from .NET 3.5