Going onto different websites you visit by clicking around on links and buttons, state transitions are taking place to transfer you to each page. Doing this transferring from page to page you observe the REST concept. It is called RESTful when you stick to the REST concept.

In the relationship between the server and the client, it is essential to use the concept of REST (representational state transfer). REST gives you a way of aligning HTTP (Hypertext Transfer Protocol) verbs and CRUD measures with each other.

It is convention to use restful routes. It is the device or repetitive design to stick to when forming routes which collaborate or communicate with the server when the HTTP request is made by the browser or client.

For a restful route to be complete it needs to do a number of things. One is to separate the client or browser from the server, it must not hold onto any information between states, it uses HTTP and HTTP methods, and must be well grounded.

Sometimes called the “Golden Seven”, there are seven RESTful routes which are traditionally utilized when creating a web application and these routes cooperate with the server. I have generated a table demonstrating the seven routes and how they are used in a dart organizing web application.

This table shows the correlation between HTTP verbs and ActiveRecord CRUD methods. You have a page to list all your darts (index), a page to present one dart (show), a page to present the new dart form (new), a page to create a new dart (create), a page to view the edit form for a dart (edit), a page to permit the user to edit an individual dart (update), and a page on which to delete a dart (destroy). These RESTful routes are mere convention and are not required to be followed, however advisable.