Skip to main content
Software Engineering

Return to Answer

edited body
Source Link
ZJR
ZJR
  • 6.3k
  • 29
  • 36

When you only plan to interact with the Microsoft stack and large-scale bandwidth consumption is not a issue, SOAP is better.

Otherwise, offering a SOAP-only API to non-Microsofters, is generally considered rude, and. And I figure there must be some dictatorial state, somewhere, where it earns you a death sentence.

When you only plan to interact with the Microsoft stack and large-scale bandwidth consumption is not a issue, SOAP is better.

Otherwise, offering a SOAP-only API to non-Microsofters, is generally considered rude, and I figure there must be some dictatorial state, somewhere, where it earns you a death sentence.

When you only plan to interact with the Microsoft stack and large-scale bandwidth consumption is not a issue, SOAP is better.

Otherwise, offering a SOAP-only API to non-Microsofters, is generally considered rude. And I figure there must be some dictatorial state, somewhere, where it earns you a death sentence.

Source Link
ZJR
ZJR
  • 6.3k
  • 29
  • 36

When you only plan to interact with the Microsoft stack and large-scale bandwidth consumption is not a issue, SOAP is better.

Otherwise, offering a SOAP-only API to non-Microsofters, is generally considered rude, and I figure there must be some dictatorial state, somewhere, where it earns you a death sentence.