Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    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. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. COIt seems like a very, very loose standard if you we want to call it that. I guess I am trying to ask, why not just call it a HTTP request. Are well named URL's the basis for a particular architecture. When I look at the twitter API "web-service", it seems like just that, a HTTP GET request, JSON output with a well-named URI path? I guess I am being too pedantic about this.
      singulars
    2. COIt is indeed loose: more like a best practice than a strict set of rules. A key thing to understand is that the statement "a HTTP request" sort of encodes within it the RESTful principles that went into designing HTTP. It's such a common practice to address resources this way that it seems obvious to us now - but it wasn't always so. Many different data transfer mechanisms on the internet - like streaming video - are not RESTful. Can you imagine the world without URLs, where your browser has to understand a different data format for every server? Totally gross.
      singulars
    3. CO@BerlinBrown - actually, your not being pedantic enough! REST is based on HTTP, but the core of the specification has to do with *alot* more than the communication transport. I recommend reading [Fielding's original dissertation](http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm) on the subject, as a start. It describes key principles of uniform interfaces, representational state, statelessness, and other key RESTful principles.
      singulars
 

Querying!

 
Guidance

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