Another blog, and a great tutorial on REST concepts
|
|
Here’s another great blog that didn’t make it into the feed that I posted earlier. It’s supposedly for people coming to Rails from .NET, but it’s pretty generally useful. Very good stuff. The best thing that I found so far on it is a 5-part series that introduces the concepts behind RESTful services. REST is basically an organized way to design your web application so that either browsers or other computers can access and manipulate the data. Essentially, you have a programming API that uses HTTP, to the same URLs that your browser uses. This (and a set of conventions) makes it trivial to understand most RESTful APIs, which is not necessarily so with alternatives like SOAP. This is all very neat because it lets you write code that accesses other peoples’ websites and data in a very simple way. Here’s the blog: And here are the REST tutorials: http://softiesonrails.com/2007/3/28/rest-101-pa… By the way, when you find a blog that you want to subscribe to, visit the home page. If your browser is firefox, you should see the little orange feed icon in the right-hand side of your address bar. Click on that, and then tell it to add the feed to your Google reader. Otherwise, there’s usually a “subscribe to this blog” button, or “RSS” or “ATOM” link somewhere on the page. Click on that to do the same thing. Worst-case scenario, you may have to paste the “RSS” link into Google reader itself. Just keep your eyes peeled for that little orange square with the radio waves—that’s the universal symbol for a feed. Also, make sure you’re on the home page when you subscribe. Otherwise, you might wind up just subscribing to the feed for that one particular post. |
|
|
In trying to wrap my head around rest concepts, I came up with the following table that sort everything nicely (for me, anyway): http://docs.google.com/View?docid=dgn2nsft_27c2… Does this make sense? Is there a better way to describe and categorize these things? Disclaimer: I plan on buying the O’Reilly RESTful Web Services book; maybe there’s a much better way to think about REST in the book. |
|
|
An idea just struck me: I think with all the RESTfulness, rails might be evolving from an MVC to an RV (resource-view) framework. What do you think? |