|This is the talk page for discussing improvements to the SOAP article.|
|WikiProject Computing||(Rated Start-class)|
Why use SOAP at all?
I find it frustrating that no-one has been able to explain to me what is the value-add of SOAP over JSON/plain XML. The only 2 advantages apply equally to plain XML and JSON. I was hoping this article would explain a bit better why anyone uses SOAP. I managed to glean the following single sentence from a 2-page StackOverflow answer: SOAP can make use of any transport protocol not just HTTP(S), SOAP offers more options when security is concerned, SOAP offers reliable messaging etc etc. What are those "options where security is concerned"? What do they mean by "reliable messaging" (over and above the features of Tcp/Ip which re-sends packets over and over if they are not being received, and ensures they arrive in the correct sequence with no errors?) What's the "etc, etc"? And who would want to use SOAP over SMTP/who would consider this an advantage?
I'm no SOAP expert but I'd bet a week's pay that the SOAPAction field shown in the example is wrong. For most SOAP 1.2 applications I would expect that field to be blank (eg. SOAPAction: "") but for most SOAP 1.1 applications it is normal to include the name of the method you are trying to fire (eg. SOAPAction: "GetStockPrice"). Comments please? Neilrieck (talk) 19:04, 13 August 2012 (UTC)
"Comparison to JSON/XML" section
The "Comparison to JSON/XML" section is full of non-sense and reads like an advert. JSON and XML are standards describing ways to represent structured data in text and SOAP is a protocol for transferring data, they're not directly comparable at all. For those reasons I removed the section. holizz (talk) 20:37, 22 November 2013 (UTC)