Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>First of all, while SOAP is specifically a web-oriented technology, REST has nothing to do with HTTP, but is still well-suited for web services. REST is also an architecture rather than a protocol, which SOAP is. So there are many ways to implement a RESTful service, as long as they adhere to the architecture's constraints.</p> <p>REST fits much better into the traditional HTTP stack since it demands correct usage of protocols, when possible. SOAP merely uses HTTP as a sort of wrapper/proxy around its own protocol, which is not what HTTP is intended for. SOAP tries to get around limitations of HTTP, but it doesn't take advantage of much of what HTTP has to offer.</p> <p>For example, cache servers sitting in the middle of a client and the content server should be able to cache requests and responses without understanding anything about the contents of each, which is not possible with SOAP, since the actual content that needs to be cached is a subset of the HTTP message's content, inside a bunch of SOAP wrappers and proprietary structure. RESTful services don't have this issue, so they scale much more naturally.</p> <p>For the best source of information on REST, read Fielding's <a href="http://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm" rel="nofollow noreferrer">dissertation</a>, and his <a href="http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven" rel="nofollow noreferrer">blog</a>, where he clears up common misconceptions. (He's the guy that created the REST specifications)</p>
    singulars
    1. This table or related slice is empty.
    1. POThumb-rules to decide between web service implementations: SOAP / REST?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USaehlke
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTDownMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTDownMod
    1. CO-1: "fits better into the traditional HTTP stack since it demands correct usage" - what does fit have to do with anything, and how would demanding correct usage accomplish it? SOAP uses HTTP as one of many possible transports, a concept that should be familiar to anyone who understands layered network protocols. Why should SOAP care about taking advantage of what HTTP has to offer? It's a _protocol_. I expect you'll only be caching GET requests and responses? What "proprietary structure"?
      singulars
      1. PO
      1. USJohn Saunders
    2. COSOAP requires POST which is defined to be uncachable. The use of the same URI for many purposes in SOAP also hinders cachcability.
      singulars
      1. PO
      1. USaehlke
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload