"We’ve seen how Peak MHz capped the speed of verbs, but nouns continued to get cheaper to store and serve." This is all good, but that's a cracking sentence.

"Little command line REST interface that you can use in pipelines." Ooh. That looks nifty.

Leonard Richardson's talk from QCon, about REST, his work on Canonical's Launchpad and its web service, and some useful history for anyone wanting to contextualise web services as part of the web.

"The other day I thought, wouldn’t it be nice if that pattern were wrapped up as a present for me (and others) to use? The answer is yes and it is named HTTParty." This is total awesome. Now I want to do more webservices hacks.

"The general rule to take from this is “dont use modules to create namespaces in controllers that are also names of pre-existing constants from other class definitions”" Matt J with some useful tips for namespaced controllers. Also, Warren G.

"If you are going to build a RESTful API, do it right. Your developers will thank you for it." Dare is right; the Newsgator REST API is very lacking, to say the least. When I used it, it even missed documented functionality.

This will come in handy, I think.

"I think there's a lot of merit in following a CRUD-based model for interacting with your application's resources. I'm not convinced all the hassle of bending dumb browser interactions into a REST-based set of verbs..."

No ActiveResource, but still some interesting patches to the RESTful behaviour in responds_to. Also... the beginnings of multibyte UTF8 support, which is great.

"I trust that the guys who wrote this have been shot. It’s not even internally consistent. And what’s with all this HTTP GET bindings. I thought GET was undefined."

A new book for O'Reilly by Leonard Richardson and Sam Ruby, which looks fantastic - both in tone and in content. Almost certain to be essential reading when it's published.

So, by adding a few controllers, I cut the total number of actions by almost twenty. That’s a pretty big deal, because actions are like moving parts in a machine—the more there are, the more can go wrong.

Matt Biddulph over at xml.com looks at making a RESTful website/app in Rails

Lots of handy things, especially scratchpads, for developing with AWS.

Really good, simply explanation, of how to write REST protocols