If we want to make a distinction between REST- and non-REST-based
Rails applications, we use the
word traditional. Traditional does not mean old or even bad, it’s only
used to make a reference to an
equivalent non-REST concept. This comparison should help to better
explain the new technology.
Feature list of REST-based Applications makes clear:
Clean URLs. REST URLs represent resources and not actions. URLs always
same format: first comes the controller and then the id of the
The requested manipulation is independent of the URL and is expressed
help of HTTP verbs.
Different Response Formats. REST controllers are developed in a way
can easily deliver their results in different response formats.
Depending on the requirements
of the client, the same action can deliver HTML, XML, RSS, or other
formats–the application becomes able to handle multiple client
Less Code. The development of multi-client-capable actions avoids
the sense of DRY2 and results in controllers having less code.
CRUD-oriented Controllers. Controllers and resources melt together
into one unit–
each controller is responsible for the manipulation of one resource
Clear Application Design. RESTful development results in a
conceptually clear and
maintainable application design.
Reference document: http://media.quilime.com/files/pdf/restful_rails_en.pdf