Lists Home |
Date Index |
Uther, James wrote:
> How is this different from REST, where an XML document of a
> specified type may be POSTed to a URL and parsed there, probably by
> the same parser? Well, one difference is that SOAP adds a bunch of
> complexity with no benefit. That's never good for security.
SOAP? All I said was Web Services. WSDL is the bit that maps XML Schema
definitions to message types, and part of its complexity is that it
includes the option of binding the message to HTPP GET or POST as well
as to SOAP though the HTTP POST binding appears to map to a
form-friendly, CGI-compatible name-value pair list rather than the
structured request block that I need in my e-commerce apps.
See http://www.esynaps.com/WebServices/WhoIsService.asmx?op=WhoIs for
some auto-generated documentation for a WSDL service, just to show
*what* the WSDL is specifying.
Would a WSDL-specified service using HTTP POST or HTTP GET count as
REST? If so (or even if not) would passing an XML request block via HTTP
POST count as REST?