Splitting hairs over "resource": the case for the affirmative (Part 2)

DABlog Splitting hairs over "resource": the case for the affirmative (Part 2):

Splitting hairs over "resource": the case for the affirmative (Part 2) April 24th, 2008 In part 1 of this two-part post, I explained my concern that the word “resource” has become too closely associated in Rails-related usage with some combination of model, database table, and controller/model stack—none of which do justice, as definitions or even first approximations, to the concept of a REST resource as originally described by Roy Fielding. Here, I’m going to expand on this observation by exploring a few ramifications of the same topic. Resources, controllers, and models (or lack thereof) As I explained in the previous post, the concept of “resource” has no database implications—indeed, no implementation implications. A resource does not have to have a corresponding model. It also does not have to have a corresponding controller. Resources are far more high-level than co...

Full article: http://dablog.rubypal.com/2008/4/24/splitting-hairs-over-...