Ummm, for the most part, REST = using HTTP as one's API (Roy Fielding gives a far more detailed description in his thesis, where he coins the term, http://www.ics.uci.edu/~taylor/documents/2002-REST-TOIT.pdf, but as Roy was one of the authors of the HTTP spec, REST is really descriptive of the architectural thinking behind HTTP).

The contrast is to things like:
- APIs within software programs
- other protocols that layer above TCP or UDP (DIS for example)
- SOAP and the W3C web services family, which layer additional protocols on top of HTTP

For the most part, if you want to retrieve JSON data, you need to use some protocol - the RESTful model is to address the data with a URL, and use an HTTP GET. If you want to upload or replace some data, you use HTTP PUT, and to delete it you use HTTP DELETE. That's about as simple as you can get.

John Carlson wrote:

PUTs, DELETEs require an id in the api, correct? Are you referring to collection identifiers? I'm talking about uploading multiple JSON objects to the server which can be done with http or REST, but http is preferred, because there is a single round trip. And yes, there's JSON coming back too (error messages).

On Feb 14, 2013 2:45 PM, "Miles Fidelman" <[email protected] <mailto:[email protected]>> wrote:

    John Carlson wrote:



        On Feb 14, 2013 12:52 PM, "Miles Fidelman"
        <[email protected]
        <mailto:[email protected]>
        <mailto:[email protected]
        <mailto:[email protected]>>> wrote:

        > Well, at least in principle, drop an html file in a
        directory (behind a server) and it gets served (or drop it in
        a WebDAV folder).

        That sounds like the web circa 1993.
        Again, you have to configure all the hyperlinks inside those
        files.

        > Again, that's why REST has largely won out over things like
        W3C web services.

        REST largely sucks because multiple objects require multiple
        round trips, which is why JSON is beating both the above.


    Ummm... JSON is a data format, REST is an API/Protocol layering
    architecture.  I know a lot of RESTful interfaces that return JSON
    payloads (CouchDB comes to mind).




-- In theory, there is no difference between theory and practice.
    In practice, there is.   .... Yogi Berra

    _______________________________________________
    fonc mailing list
    [email protected] <mailto:[email protected]>
    http://vpri.org/mailman/listinfo/fonc



_______________________________________________
fonc mailing list
[email protected]
http://vpri.org/mailman/listinfo/fonc


--
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra

_______________________________________________
fonc mailing list
[email protected]
http://vpri.org/mailman/listinfo/fonc

Reply via email to