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]> wrote:
> John Carlson wrote: > >> >> >> On Feb 14, 2013 12:52 PM, "Miles Fidelman" >> <[email protected]<mailto: >> mfidelman@**meetinghouse.net <[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] > http://vpri.org/mailman/**listinfo/fonc<http://vpri.org/mailman/listinfo/fonc> >
_______________________________________________ fonc mailing list [email protected] http://vpri.org/mailman/listinfo/fonc
