REST, APIs continued

A Conversation about REST with my brother

An explanation about the very very backbone of the internet’s means and ways of communicating one to another. It seems that REST, at it’s very base, is a small set of commands with which to communicate and coordinate resources from one point to another, in some manner (be it hypertext, JSON, XML, or some other predetermined format). REST stands for REpresentational State Transfer, and from handing content one to another, modifying that content some way or another, and potentially returning it.

For some while, the internet seemed to have a bit more “wild west” approach to using this, but it has since calmed down, and the conversation ended with a note saying that this has quieted down and Ruby is used mostly to do a good job of making RESTful data (or, data RESTful?).

SuperAgent

Bookmarked. This seems to be a way to manage the backend via JavaScript, but I am at a loss what it is exactly organizing or … re-parsing … into JavaScript to begin with. So at the moment, it’s making it easier for me to not understand what is going on any. Additional class time will enlighten me to it’s machinations.

---

API Keys: Complete