Timeline for What are the deciding factors in choosing to expose a web service as a SOAP or REST service?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 23, 2016 at 7:07 | comment | added | maaartinus | I'm afraid every true statement about SOAP must read as a rant. It's enterprisey by design and gives you tons of options where you just want to send some data. Concerning the few SOAP interfaces I worked with, each was a highly redundant mess (not exactly SOAP's fault, but the affinity to SOAP correlates with the affinity to bloatware). Sorry for ranting. | |
| Nov 22, 2016 at 12:38 | comment | added | David Tonhofer | We had the same complaint with CORBA/IDL back in the 90s. Then suddenly "Simple Object Access Protocol" .. it will be simple! It will be cool! It will be fast. Ten years later, it is considered too complex. Along comes JSON (IMAO really a square wheel for data transfer operations in student lab settings or restricted "I know what I'm doing" quick fix situations) and RESTful ops. Rinse, repeat... | |
| Mar 25, 2015 at 13:56 | comment | added | Cornel Masson | You're right. Sorry, I was awash in SOAP soup at the time :D | |
| Feb 26, 2015 at 15:37 | comment | added | gnat | this reads more like a rant, see How to Answer | |
| Feb 26, 2015 at 12:26 | review | First posts | |||
| Feb 26, 2015 at 12:35 | |||||
| Feb 26, 2015 at 12:24 | history | answered | Cornel Masson | CC BY-SA 3.0 |