Why isn't SOAP

 

I understand RESTful is an architecture style, but what exactly makes SOAP-based web service not count for RESTful?

It's not clear to me which points below (from Wikipedia), is not conformed by SOAP.

  • Client-server
  • Stateless
  • Cacheable
  • Layered system
  • Code on demand (optional)
  • Uniform interface
  • Identification of resources
  • Manipulation of resources through these representations
  • Self-descriptive messages
  • Hypermedia as the engine of application state

    • EDIT : I just came across this which summaries it pretty well.

    REST is not RPC, RPC says, "define some methods that do something" whereas REST says, "define some resources and they will have these methods". It is a subtle but vital difference, when given a URI anyone knows they can interact with it via the predefined set of methods and receive standard HTTP responses in return. So given http://www.peej.co.uk/ I know I can issue a GET on it and receive something meaningful back. I may then try a PUT on it to change it and receive a meaningful HTTP error code since I'm not authorised to meddle with it.

    SOAP follows the RPC pattern. A SOAP API describes a series of methods, along with their parameters and return values, that you can call from your code. There's a marshaling step that converts this into it's network representation.

    REST is never RPC. A REST API describes a series of resources, along with a set of verbs (typically HTTP's GET, POST, PUT, DELETE) that can act on them.

    To answer your question directly: SOAP primarily violates point 6 (it doesn't provide a uniform set of verbs across APIs). It also violates point 2 (the server can maintain state for each client), and as a result point 3 as well (state prevents caching).

    REST and SOAP are not equivalent concepts.

    REST:

  • Depends on one transport protocol (HTTP).
  • Makes full use of the specific features of that protocol (verbs GET, POST, PUT, DELETE, caching, headers, and predefined error codes).
  • Says nothing about the format of the messages passed back and forth. However, since the HTTP verb and URL already define the action to take, the message body must therefore contain only the data.
  • Message security is provided by the transport protocol (HTTPS), and is point-to-point only. If you want to secure the message end-to-end, you have to do it yourself.
  • Originally intended for simple CRUD operations on objects.

    • SOAP:

  • Independent of the transport protocol (could be HTTP, FTP, TCP, UDP, named pipes, shared memory or even email).
  • Requires only that the transport protocol be able to send and receive text (eg on HTTP, only the POST verb is used).
  • Strictly defines the format of the messages passed back and forth. A SOAP message contains the data, the action to perform on it, the headers, and the error details in case of failure.
  • Message security is provided by the WS-* standards, and is end-to-end.
  • Originally intended for arbitrary RPC calls.

    • Items 2 and 3 in the above lists are the main points of incompatibility.

    One of the objectives of REST is cachability, for that the resource needs to be identified by the uri (query string). In soap the request is posted, therefor for different requests you have the same uri and thus the resource cannot be uniquely identified by the ur

    链接地址: http://www.djcxy.com/p/71428.html

    上一篇: RESTful比SOAP快吗？ 以及何时使用其中之一？

    下一篇: 为什么不是SOAP